MCP.Market

Agentforge MCP server

online · 100% uptime
by acarchidi·io.github.acarchidi/agentforge·v1.9.0

DeFi safety for AI agents: signature + tx checks, sanctions, rug checks, launch feed. 26 tools.

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Agentforge yet.

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

Agentforge tools

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

Not scanned yet. New listings are scanned within a day or two of arriving.

How Agentforge compares

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

Safety score
87/100
higher than 73% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
195 ms
faster than 64% of 30,031 servers

Release history: 3 versions in the registry since 2026-07-08, latest 2026-11-03, typically one every 118 days.

Install Agentforge in Claude Code, Cursor or VS Code

claude mcp add --transport http agentforge https://agentforge-taupe.vercel.app/mcp
Add to Cursor

Agentforge: common questions

Is Agentforge MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Agentforge safety report
How do I install Agentforge?
It runs remotely at agentforge-taupe.vercel.app. 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 Agentforge need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Agentforge maintained?
The last commit was 119 days ago (2026-07-08). The latest release is v1.9.0.
Is Agentforge up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Agentforge compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 195 ms (faster than 64% of 30,031 servers). Full comparison.