
Agent Teller
io.github.sarduine13-starPublished by GitHub account sarduine13-starv1.1.0Updated Oct 24, 2026
Verify AI agent payments and detect fraud. Input: agent_id, amount, service_id.
Overview
A remote MCP endpoint for verifying AI agent payments and detecting fraud, taking an agent ID, amount and service ID as input.
- What you can do
- Verify AI agent payments and check them for fraud, using an agent identifier, a payment amount and a service identifier as the inputs. The manifest lists no individual tools, so the exact operations are not documented; the description only covers payment verification and fraud detection.
- When to use it
- Relevant when an assistant needs to check or validate payments attributed to AI agents, or to screen such transactions for suspected fraud.
- Requirements
- A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. The manifest declares no authentication, so no credentials are described.
Installation
In SourceWeft
- Open Agent Teller in the dashboard and add it to a workspace.
- 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/io.github.sarduine13-star%2Fagent-teller/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"agent-teller": {
"type": "http",
"url": "https://agent-teller-production.up.railway.app/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
60% 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
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.