Mmcp.market

Token Safety & Contract Risk API MCP server

not responding
by Br0ski777·io.github.Br0ski777/token-safety·v1.1.0

Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402.

D47/100grade D
What users say
No reviews yet
Be the first
Safety scan
D47/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Token Safety & Contract Risk API yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Token Safety & Contract Risk API tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

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

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote unreachable: TypeError: fetch failed0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 20 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    TypeError: fetch failed

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

Install Token Safety & Contract Risk API in Claude Code, Cursor or VS Code

claude mcp add --transport http token-safety https://token-safety.api.klymax402.com/mcp
Add to Cursor

Token Safety & Contract Risk API: common questions

Is Token Safety & Contract Risk API MCP server safe?
Not recommended: it is graded D (47/100). Read the Token Safety & Contract Risk API safety report
How do I install Token Safety & Contract Risk API?
It runs remotely at token-safety.api.klymax402.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Token Safety & Contract Risk API need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Token Safety & Contract Risk API maintained?
The last commit was 25 days ago (2026-09-02). The latest release is v1.1.0.
Is Token Safety & Contract Risk API up?
0% of our last 28 checks got an answer. We check remote servers about four times a day.

More from Br0ski777 →