com.obsmetrics.paygent/agents
REMOTE · PAYGENT.OBSMETRICS.COM
Pay-per-call safety guards for AI agents: injection, tool-call, signing, secret, x402-trust.
Available components
Last scanned (10 hours ago)
Scores higher than 4% of remote servers
Unreachable for 3 days in a row. Last reached 2 Nov 2026.
Category Security
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 16 Oct 26 −5
- HTTPS: pass → unverified ▼ security
- 14 Oct 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 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
- 25 Sept 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
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 26 0
- Stability: pass → 0.83 functional
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 5 Nov 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 | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 538326a228dea9430ff3c0032d7e3223300 |
| 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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://paygent.obsmetrics.com/mcp | HTTPS enforced |
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 →
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]
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The untrusted text to scan before you feed it to your LLM. |
| context | string | – | Optional: 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]
| Name | Type | Req | Description |
|---|---|---|---|
| diff | string | yes | Unified git diff to summarise |
| style | string | – | e.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]
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The 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]
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code or unified diff to review |
| context | string | – | Optional context about the code |
| language | string | – | Language 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]
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional free-form context. |
| expected | object | – | Your 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`. |
| spendPolicy | object | – | Optional buyer spend policy (context only). |
| tx | object | – | An EVM transaction you are about to sign. |
| typedData | object | – | An 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]
| Name | Type | Req | Description |
|---|---|---|---|
| call | object | yes | The tool call you are about to execute. |
| context | string | – | Optional: where the task/input came from (untrusted source label). |
| expected | object | – | Machine-checkable constraints. Supplying them lets the verdict BIND the call; only a positively-scoped, satisfied call is auto-exec-safe. |
| intent | string | – | What 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]
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional free-form context. |
| endpointUrl | string | – | Resource URL being paid (context only; never fetched). |
| expected | object | – | Optional caller expectations. |
| paymentPayload | – | – | The 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… |
| paymentRequirements | – | yes | The x402 payment requirements from the counterparty: the 402 `accepts` array, or a single object. |
| selectedOptionIndex | number | – | Index in the accepts array the buyer intends to settle (default 0). The verdict is scoped to it. |
| serverMetadata | – | – | Optional server metadata the caller already holds (context only; not fetched). |
| spendPolicy | object | – | Optional buyer spend policy to evaluate against and to pin facilitators. |
No output schema declared.
No examples provided.
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
claude mcp add --transport http com-obsmetrics-paygent-agents 'https://paygent.obsmetrics.com/mcp'
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 14 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?
Its publisher declares no required credentials for com.obsmetrics.paygent/agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the com.obsmetrics.paygent/agents MCP server still maintained?
com.obsmetrics.paygent/agents is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 2 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.