MCP server for Match It Up NetworkBot — browse members, get matches, post signals, send DMs
agent-tools (x402 + MCP + A2A directory) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open InstallationWhat it does
Discover x402 services, MCP servers and A2A agents by intent — agent-tools.cloud directory.
Quickstart
# 1 — run it from where its publisher ships it
uvx agent-tools-mcp
# 2 — ask your agent something
> Discover x402 services, MCP servers and A2A agents by intent — agent-tools.cloud directory.
agent-tools (x402 + MCP + A2A directory) is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way, and that is the choice that matters: behind our gateway it runs on the publisher’s own infrastructure and nothing of it touches your machine, while locally it starts as a process under your own user, with your files and your network.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add agent-tools-x402-mcp-a2a-directory -- uvx agent-tools-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find x402 / MCP services matching an intent or filter set.
No parameter schema on file.
LLM-ranked recommendation of the best x402/MCP services for an intent.
No parameter schema on file.
Get full details + ready-to-paste call template for a service by slug.
No parameter schema on file.
List all directory categories.
No parameter schema on file.
Directory size, healthy count, source breakdown.
No parameter schema on file.
Search the standalone MCP server directory (registry / Smithery / PulseMCP).
No parameter schema on file.
Get the full card for one MCP server by slug.
No parameter schema on file.
Find A2A agents you can delegate a task to.
No parameter schema on file.
Unified search across x402 services, MCP servers and A2A agents.
No parameter schema on file.
Check an MCP server (by endpoint URL) for malware / prompt-injection / tool-poisoning: returns our stored verdict if indexed, else probes + scans + indexes it.
No parameter schema on file.
Self-register an x402 / MCP service for human review.
No parameter schema on file.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. agent-tools (x402 + MCP + A2A directory) costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (2 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| analyze_eth_transaction | no tags | |
| chat_with_near_assistant | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.2.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Writing one takes an account with at least 50 real tool calls against agent-tools (x402 + MCP + A2A directory) in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.