Agents

com.obsmetrics.paygentPublished by paygent.obsmetrics.comOfficial publisherv0.0.8Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint offering pay-per-call safety guards for AI agents, covering injection, tool-call, signing, secret and x402-trust checks.

What you can do
This server exposes safety-guard capabilities for AI agents, described as covering injection, tool-call, signing, secret and x402-trust checks. It runs as a remote streamable HTTP endpoint rather than a local package. No individual tools are listed in the supplied manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant or agent pipeline to route safety checks through a hosted service instead of implementing them locally. It may suit teams already working with x402-style payment or trust flows. Because the tool list is not published, verify the actual capabilities before relying on it.
Requirements
A remote streamable HTTP connection to the provider's endpoint. No packages, environment variables, headers or authentication are declared in the manifest, but the endpoint may still require credentials or payment in practice.
Before you install
The description indicates pay-per-call usage, so calls may incur charges; confirm pricing and limits first. It is described as handling signing and secret checks, which implies sensitive material may pass through a third-party service. No authentication is declared, so verify how access and data are protected before sending anything confidential.

Installation

In SourceWeft

  1. Open Agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.obsmetrics.paygent%2Fagents/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.0.8LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.