MCP.Market

Is Bounty API MCP server safe?

Probably. Read the findings first.

C64/100grade C

Use with care. Some checks failed or could not be verified.

What to know before installing
  • highRemote endpoint did not respond — Streamable HTTP error: Error POSTing to endpoint: {"detail":"Method Not Allowed"}

How Bounty API compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
64/100
higher than 19% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 high
  • Code scan3 source files scanned25/25
  • Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: {"detail":"Method Not Allowed"}0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 10 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    Streamable HTTP error: Error POSTing to endpoint: {"detail":"Method Not Allowed"}

Overall 64/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Bounty API reviews, tools and install