Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/kevinfee3/authoryze-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/kevinfee3/authoryze-mcp/authoryze)<a href="https://agentmods.dev/mcp/kevinfee3/authoryze-mcp/authoryze"><img src="https://agentmods.dev/badge/mcp/kevinfee3/authoryze-mcp/authoryze.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
authoryze scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 6 lines scan A 27dc192fc1eb
authoryze is an MCP server published in the GitHub repository kevinfee3/authoryze-mcp (0 stars, last pushed 15d ago), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-moonpay
MCP server for MoonPay — fiat-to-crypto on/off-ramp, 100+ assets; Pix for Brazil onramp. Runs locally from the @codespar/mcp-moonpay npm package. Needs 6 environment variables to run.
mcp-itau
MCP server for Itaú Unibanco — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS). Runs locally from the @codespar/mcp-itau npm package. Needs 5 environment variables to run.
mcp-rinne
Brazilian card acquiring API — merchants, cards-on-file, 3DS, PIX, banking, pricing. Runs locally from the @codespar/mcp-rinne npm package. Needs 5 environment variables to run.
mcp-adyen
MCP server for Adyen Checkout API v71 — enterprise payments (iFood, Uber, Spotify in LatAm). Runs locally from the @codespar/mcp-adyen npm package. Needs 4 environment variables to run.
mcp-banco-do-brasil
MCP server for Banco do Brasil — Pix, Cobrança (boleto), Conta-Corrente, Arrecadação (OAuth2 + mTLS). Runs locally from the @codespar/mcp-banco-do-brasil npm package. Needs 6 environment variables to run.
mcp-bigdatacorp
MCP server for BigDataCorp — Brazilian data enrichment + KYC (CPF/CNPJ/vehicle/property/antifraud). Runs locally from the @codespar/mcp-bigdatacorp npm package. Needs 3 environment variables to run.