Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.obsmetrics.paygent/agents

REMOTE · PAYGENT.OBSMETRICS.COM · SCANNED SEP 20

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

−2 this week 75 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1589 tokens (~227/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the com.obsmetrics.paygent/agents MCP server?

com.obsmetrics.paygent/agents is a hosted endpoint at https://paygent.obsmetrics.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · paygent.obsmetrics.com

# add to Claude Code
claude mcp add --transport http com-obsmetrics-paygent-agents 'https://paygent.obsmetrics.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-obsmetrics-paygent-agents": {
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-obsmetrics-paygent-agents": {
      "type": "http",
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-obsmetrics-paygent-agents]
url = "https://paygent.obsmetrics.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-obsmetrics-paygent-agents": {
      "type": "remote",
      "url": "https://paygent.obsmetrics.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-obsmetrics-paygent-agents --url 'https://paygent.obsmetrics.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-obsmetrics-paygent-agents:
    url: "https://paygent.obsmetrics.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-obsmetrics-paygent-agents": {
      "Transport": "http",
      "Url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-obsmetrics-paygent-agents -t streamable-http -u 'https://paygent.obsmetrics.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-obsmetrics-paygent-agents": {
      "type": "http",
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 3 Sept 26 0
    • Stability: 0.97 → pass security
  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Sept 26 −1
    • Stability: pass → 0.93 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +53
    • Stability: unverified → pass security
    • HSTS header: fail → pass security
    • Transport: fail → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail functional
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
  • 20 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.80 → unverified security
    • Transport: pass → fail security
    • HSTS header: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: fail → unverified functional
    • Tool coverage: 100 → unverified functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://paygent.obsmetrics.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=obsmetrics.com CN=YE2,O=Let's Encrypt,C=US 23 Aug 2026 21 Nov 2026 ECDSA 256 ECDSA-SHA384 5efe7db2c14f63db90e976b14fe233f2d40
SANs: *.obsmetrics.com, obsmetrics.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of paygent.obsmetrics.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
obsmetrics.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://paygent.obsmetrics.com/mcp Verified 200
http (plaintext) http://paygent.obsmetrics.com/mcp HTTPS enforced
MCP tools · 7 exposed · ~1,545 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
inject-guard ~221

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]

NameTypeReqDescription
contentstringyesThe untrusted text to scan before you feed it to your LLM.
contextstringOptional: where the content came from (url, tool name, sender) - context only.

No output schema declared.

No examples provided.

pr-summary ~62

Turn a git diff into a clear PR description or release notes. [dev-tools; up to 30c/call]

NameTypeReqDescription
diffstringyesUnified git diff to summarise
stylestringe.g. conventional, changelog, executive

No output schema declared.

No examples provided.

secret-scan ~222

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]

NameTypeReqDescription
contentstringyesThe text to scan for leaked secrets (diff, config, .env, log line, LLM output).

No output schema declared.

No examples provided.

secure-code-review ~84

Security review of a code snippet or diff. Returns structured findings (severity, CWE, location, remediation). [security; up to 75c/call]

NameTypeReqDescription
codestringyesSource code or unified diff to review
contextstringOptional context about the code
languagestringLanguage hint, e.g. typescript, python

No output schema declared.

No examples provided.

sign-guard ~327

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]

NameTypeReqDescription
contextstringOptional free-form context.
expectedobjectYour stated intent. Supplying it lets the verdict BIND the action; only a fully bound, clean action is auto-sign-safe. For an allowance, you MUST supply maxAmount; for a transferFrom, supply `from`.
spendPolicyobjectOptional buyer spend policy (context only).
txobjectAn EVM transaction you are about to sign.
typedDataobjectAn EIP-712 message you are about to sign (the off-chain drainer surface: permit, Permit2, EIP-3009). { domain, types, primaryType, message }.

No output schema declared.

No examples provided.

tool-call-guard ~295

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]

NameTypeReqDescription
callobjectyesThe tool call you are about to execute.
contextstringOptional: where the task/input came from (untrusted source label).
expectedobjectMachine-checkable constraints. Supplying them lets the verdict BIND the call; only a positively-scoped, satisfied call is auto-exec-safe.
intentstringWhat this call is for (natural language). Used by the classifier for intent-mismatch.

No output schema declared.

No examples provided.

x402-trust-audit ~334

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]

NameTypeReqDescription
contextstringOptional free-form context.
endpointUrlstringResource URL being paid (context only; never fetched).
expectedobjectOptional caller expectations.
paymentPayloadThe UNSIGNED EIP-3009 authorization the buyer is about to sign: { authorization|message: {from,to,value,validAfter,validBefore,nonce}, domain: {name,version,chainId,verifyingContract} }. Lets the aud…
paymentRequirementsyesThe x402 payment requirements from the counterparty: the 402 `accepts` array, or a single object.
selectedOptionIndexnumberIndex in the accepts array the buyer intends to settle (default 0). The verdict is scoped to it.
serverMetadataOptional server metadata the caller already holds (context only; not fetched).
spendPolicyobjectOptional buyer spend policy to evaluate against and to pin facilitators.

No output schema declared.

No examples provided.

Common questions

What is the com.obsmetrics.paygent/agents MCP server?

com.obsmetrics.paygent/agents is an MCP server listed in the public MCP registry as com.obsmetrics.paygent/agents. Pay-per-call safety guards for AI agents: injection, tool-call, signing, secret, x402-trust. This page covers its hosted endpoint (https://paygent.obsmetrics.com/mcp).

Is the com.obsmetrics.paygent/agents MCP server safe to use?

com.obsmetrics.paygent/agents scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.obsmetrics.paygent/agents MCP server expose?

com.obsmetrics.paygent/agents exposes 7 tools: secure-code-review, pr-summary, x402-trust-audit, sign-guard, inject-guard, and 2 more. Their descriptions and schemas cost roughly 1,545 tokens of context every time the server is loaded.

Does the com.obsmetrics.paygent/agents MCP server require authentication?

No. We connected to com.obsmetrics.paygent/agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.obsmetrics.paygent/agents MCP server still maintained?

com.obsmetrics.paygent/agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.