io.github.manteclaw/base-agent-kit
Base L2 Agent Kit
Is the Base L2 Agent Kit MCP server down? Yes. It has given no valid answer since 2026-11-04: not found.
MCP server for Base L2 DeFi operations with 9 monetized endpoints
not found down since 2026-11-04 · probed 2026-11-14 · unchanged since 2026-11-11
download answered HTTP 404
- Bundle
- https://github.com/manteclaw/litcoiin-solutions/releases/download/mcp-v1.0.0/base-agent-kit.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/manteclaw/litcoiin-solutions
- Registry
- active, updated 2026-05-05 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- Money Reactor io.github.makar52nn2016-jpg/money-reactor · not found
- X Archive RAG io.github.mameshivaa/x-archive-rag · not found
- Kato io.github.manduks/kato · alive
- LLM Provider MCP io.github.manishiitg/llm-provider-mcp · crashed on start
- io.github.many77146-bot/dmt-receipts · alive
- Axialis IconVectors MCP io.github.marcemile/iconvectors-mcp · error
- AI Model Watch io.github.markksantos/ai-model-watch · alive
- Caption Checker io.github.markksantos/caption-checker · alive
Servers that mention base.
- Aevia ai.aeviamodeler/aevia · needs auth
- 1325.AI ai.1325/mcp · needs auth
- ai.argushq/enforcement-database · no DNS
- Knowledge Base ai.b77/knowledge-base · needs auth
- ai.baselight/baselight · no DNS
- ai.basethread/basethread · needs auth
- brainattic ai.brainattic/knowledge-base · needs auth
- ColdState — Deterministic Knowledge Infrastructure ai.coldstate/knowledge · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-04, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.