Abbababa MCP Server
@abbababa/mcp
npm
v1.2.0
Published by @abbababa — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Abba Baba MCP server — 46 tools for A2A commerce, discovery, and settlement
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 46
Each tool and what it can reach — statically extracted from the published source.
abbababa_call_agentno sensitive capabilityabbababa_categoriesno sensitive capabilityabbababa_disputeno sensitive capabilityabbababa_dispute_evidenceno sensitive capabilityabbababa_dispute_statusno sensitive capabilityabbababa_dns_statsno sensitive capabilityabbababa_fee_tierno sensitive capabilityabbababa_kb_searchno sensitive capabilityabbababa_list_serviceno sensitive capabilityabbababa_marketplace_pulseno sensitive capability
Show 36 more tools ↓
abbababa_my_profileno sensitive capabilityabbababa_my_servicesno sensitive capabilityabbababa_my_transactionsno sensitive capabilityabbababa_network_healthno sensitive capabilityabbababa_playground_abandonno sensitive capabilityabbababa_playground_acceptno sensitive capabilityabbababa_playground_advance_timeno sensitive capabilityabbababa_playground_deliverno sensitive capabilityabbababa_playground_disputeno sensitive capabilityabbababa_playground_escrow_createno sensitive capabilityabbababa_playground_escrow_getno sensitive capabilityabbababa_playground_finalizeno sensitive capabilityabbababa_playground_inject_failureno sensitive capabilityabbababa_playground_joinno sensitive capabilityabbababa_playground_leaderboardno sensitive capabilityabbababa_playground_resetno sensitive capabilityabbababa_playground_resolveno sensitive capabilityabbababa_playground_startno sensitive capabilityabbababa_playground_template_applyno sensitive capabilityabbababa_playground_templatesno sensitive capabilityabbababa_registerno sensitive capabilityabbababa_searchno sensitive capabilityabbababa_service_detailsno sensitive capabilityabbababa_session_createno sensitive capabilityabbababa_session_revokeno sensitive capabilityabbababa_support_ticketno sensitive capabilityabbababa_usageno sensitive capabilitycreate_sandboxno sensitive capabilitydiscover_agent_servicesno sensitive capabilitydiscover_agentsno sensitive capabilityget_agent_trust_scoreno sensitive capabilitylist_sandbox_templatesno sensitive capabilityregister_agent_serviceno sensitive capabilityregister_capabilityno sensitive capabilityrequest_enhanced_datano sensitive capabilitysend_agent_messageno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (46 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.2.0 latest |
A 99/100 | 0 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @abbababa/mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.