mcpbeat Sign in

Agents MCP Server

by obsmetrics-paygent Your server? Claim it
not responding

Agents is listed as active in the registry but did not answer our last check. It exposes 7 tools.

Pay-per-call safety guards for AI agents: injection, tool-call, signing, secret, x402-trust.

Uptime history 91 days of history · worst day 0%
91 days agonow
0.0%
Uptime 24h
0 of 92 checks
7
Tools
read from the server
20000 ms
Response time
average over 24h
open, no key
Access
streamable-http

Agents does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add agents --transport http https://paygent.obsmetrics.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://paygent.obsmetrics.com/mcp
~/.codex/config.toml
[mcp_servers.agents]
url = "https://paygent.obsmetrics.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agents": {
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agents": {
      "type": "http",
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inject
inject-guard
Untrusted-content guardrail for agents: submit a blob of text you are about to feed to your own LLM (scraped web content, a tool result, another agent's message) and get a machine-enforceable verdict - is this a prompt-injection / jailbreak / data-exfiltration / tool-hijack attempt? Returns a risk level, the detected classes with spans, the unicode obfuscation it found (zero-width, bidi-override, tag-chars, homoglyphs), and a SANITIZED copy safe to feed onward. Hybrid: a deterministic, uninjectable pattern engine (authoritative) plus an LLM classifier that can only raise the risk, never clear a flag. Detection of known injection classes - not a proof of safety. [security; up to 15c/call]
secret
secret-scan
Leaked-credential guardrail for agents: submit a blob you are about to commit, log, post, or hand to another tool (a diff, a config, an .env, an LLM output) and get a machine-enforceable verdict - does it contain a live secret? Detects cloud keys (AWS), VCS tokens (GitHub/GitLab), provider API keys (Stripe, OpenAI, Anthropic, Google, Slack), private-key blocks, JWTs, and credentials embedded in URLs, plus high-entropy key=value assignments. Returns a risk level, the detected classes with a MASKED locator (never the secret itself, so the verdict cannot re-leak), and a REDACTED copy safe to emit onward. Deterministic, sub-second, never fetches. Detection of known secret formats - not a proof of cleanliness. [security; up to 200c/call]
secure
secure-code-review
Security review of a code snippet or diff. Returns structured findings (severity, CWE, location, remediation). [security; up to 75c/call]
sign
sign-guard
Pre-sign safety oracle for agent wallets: submit the transaction or EIP-712 message you are about to sign and get a machine-enforceable verdict. Decodes the calldata/typed-data, flags the drainer toolkit (unlimited approvals, setApprovalForAll, permit/permit2 + EIP-3009 to an unexpected party, transferFrom draining an unnamed account, ownership transfer, raw ETH to a stranger), and binds the decoded action to your stated intent - only a fully pinned, clean action is auto-sign-safe. Fails closed: an undecodable on-chain call is cautioned and an unrecognized off-chain signature grant is blocked. Deterministic, sub-second, no endpoint fetch. It vouches that the action matches what you said; it does NOT vouch that a counterparty is trustworthy. [security; up to 200c/call]
summary
pr-summary
Turn a git diff into a clear PR description or release notes. [dev-tools; up to 30c/call]
tool
tool-call-guard
Pre-execution safety oracle for agent actions: submit the tool call you are about to run (shell, http, sql, file, code, env) plus your stated intent, and get a machine-enforceable verdict before you execute it. Decodes what the call does, flags the danger toolkit (rm -rf, reverse shell, curl|sh, SSRF to cloud metadata, credential reads, DROP/DELETE-without-WHERE, path traversal, dynamic eval), and binds it to your intent (allowedHosts/allowedPaths/readOnly/noNetwork) - only a fully pinned, clean, intent-matched call is auto-exec-safe. Hybrid: a deterministic, uninjectable detector engine (authoritative) plus an LLM classifier that can only raise the risk. Fails closed. Detection of known-dangerous patterns, not a proof of safety; it never executes the call. [security; up to 8c/call]
x402
x402-trust-audit
Vet an x402 counterparty before settling USDC: scores the advertised payment requirements AND (when supplied) the EIP-3009 authorization you are about to sign. Returns a machine-enforceable trust verdict (per-entry scores, coverage-honest trustScore, spend-constraint + tamper-evident fingerprint) for buyer agents and wallet/spend-policy layers. No endpoint fetch. [security; up to 200c/call]

Endpoints

URLTransportStateLatencyChecked
https://paygent.obsmetrics.com/mcp streamable-http answering 20000 ms 3 min ago

Alternatives to Agents

same job, measured the same way
Holster MCP
by nautaai

Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.

117 installs/wk local only
x402 Agent Tools
by signal-forge-ai

Pay-per-call web, Base onchain and crypto-alert tools for agents. USDC on Base via x402, no API key.

9 tools answering
Queryshield
by bch1212

Secure SQL proxy for AI agents — NL→SQL, AST safety, per-agent RLS, audit log.

97 installs/wk local only
Tokenectomy Razor
by daffa2555

Autonomous log surgery & secret redaction MCP server for AI coding agents.

local only
R
RWA Data MCP Server
by daveabear

Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402.

9 tools answering
DropEngine x402 Agent Services
by ahmet11159

AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.

24 tools answering
Quill
by manumarri-sudo

Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.

104 installs/wk local only
A
AgentShield
by atmflow55

Smart contract security for AI agents — verify, monitor, freeze, x402 payments

43 installs/wk local only

Agents — questions

Answers built from our own checks of this server.

What can Agents do?
It exposes 7 tools, read directly from the server on our last check. Among them: inject-guard, pr-summary, secret-scan, secure-code-review, sign-guard, tool-call-guard and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 20000 ms. The bar chart above shows every period we have measured.
The registry lists Agents as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Agents?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agents need an API key?
No. Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.