INDIVIDUAL MCP TOOL

secure-code-review

Security review of a code snippet or diff.

obsmetrics.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://paygent.obsmetrics.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for secure-code-review and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.paygent]
url = "https://paygent.obsmetrics.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "paygent": {
      "type": "http",
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: paygent
Remote MCP URL: https://paygent.obsmetrics.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "paygent": {
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "paygent": {
      "type": "http",
      "url": "https://paygent.obsmetrics.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "paygent",
  "transport": "streamable-http",
  "url": "https://paygent.obsmetrics.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

pr-summary — Turn a git diff into a clear PR description or release notes.
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.
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.
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?
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.
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 .