agent-exporter MCP bridge runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 27 May 2026.
Local stdio MCP bridge for archive publishing, retrieval, and governance evidence.
Nothing serious here today
Today is the operative word: we check agent-exporter MCP bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to agent-exporter MCP bridge
same job, measured the same wayMCP stdio server for Attestify OS — governed agent execution and Attestify Trust signed evidence.
SEAM: local-first memory runtime for AI agents, with retrieval and glassbox provenance over MCP.
Local stdio MCP bridge for XCREENER's XQL screener API — validate, explain, and run queries.
ArkHive MCP: governed, tamper-evident local memory for AI agents. Where context gives meaning.
Give an AI agent a real .NET debugger: breakpoints, stepping, locals, expression evaluation.
Shared, versioned knowledge for AI coding agents: cited retrieval and publishing of OKF bundles.
Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
Open scientific and engineering knowledge for AI agents: search, evidence, document publishing.
agent-exporter MCP bridge — questions
Answers built from our own checks of this server.