Is io.github.xiaojiou176-open/agent-exporter-mcp safe to use?

io.github.xiaojiou176-open/agent-exporter-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.xiaojiou176-open/agent-exporter-mcp?

io.github.xiaojiou176-open/agent-exporter-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.

Is io.github.xiaojiou176-open/agent-exporter-mcp actively maintained?

io.github.xiaojiou176-open/agent-exporter-mcp is actively maintained — last commit was 1 day ago. It has 1 GitHub stars.

io.github.xiaojiou176-open/agent-exporter-mcp

Local stdio MCP bridge for archive publishing, retrieval, and governance evidence.

ActiveNot tested

Legal

★ 1GitHub

28DNo CVEsactive

Quick Install

{
  "mcpServers": {
    "io-github-xiaojiou176-open-agent-exporter-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Setup guide

No install config available. Check the server's README for setup instructions.

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-xiaojiou176-open-agent-exporter-mcp)](https://mcppedia.org/s/io-github-xiaojiou176-open-agent-exporter-mcp)

Should you use this server?

Local stdio MCP bridge for archive publishing, retrieval, and governance evidence.

✓

Is it safe?

No package registry to scan.

No authentication — any process on your machine can connect.

License not specified.

✓

Is it maintained?

Last commit 1 days ago. 1 stars.

Will it work with my client?

Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

README

agent-exporter

agent-exporter is an archive and governance workbench for AI agent transcripts.

Try It In 3 Steps · Zero-Context First Look · Docs Landing · Archive Shell Proof · Latest Release

Front Door Map

If you only remember four things, remember these:

Question	Short answer
What is this?	an archive and governance workbench for AI agent transcripts
What should I do first?	start with the quickstart path
What is the first visible proof?	one HTML transcript receipt plus the archive shell proof
What shape should I expect?	an inspectable archive workbench, not a hosted archive platform or generic MCP product

Product Kernel

The simplest way to understand this repo is:

It turns transcript export, archiving, retrieval, evidence, and governance into an inspectable archive workbench first, instead of pretending to be a hosted service or remote platform.

Surface Model

Primary entrypoint: CLI quickstart
Secondary Surface 1: local archive shell / reports shell
Secondary Surface 2: repo-owned integration pack
Secondary Surface 3: read-only governance MCP bridge
Secondary Surface 4: root-level MCP descriptor for registry/read-back lanes (server.json)

These surfaces can coexist, but they cannot borrow authority from each other. Secondary operator-facing surfaces must not replace the current primary front door.

Flagship Public Packet

The flagship public packet for the current stage is:

GitHub repo + CLI quickstart + archive shell proof

That does not mean the other surfaces do not matter. It means each surface must clear its own review line, instead of turning a partial secondary readiness signal into a repo-wide public-ready claim.

Front Door Today

If this is your first visit, use the repo in this order:

Start with the CLI quickstart
Then inspect the archive shell proof
Only then branch into reports shell, integration pack, or governance lanes as needed

In plain English:

The product kernel already includes evidence and governance, but the public front door still needs the quickstart path to own the first screen.

Who This Repo Is For

Use this repo if your real question sounds like one of these:

"Can I export one AI agent transcript into a local artifact I can read and keep?"
"Can I turn multiple transcript artifacts into a local archive shell instead of a hosted service?"
"Can I keep retrieval, integration evidence, and governance attached to the same local workbench?"

If your first instinct is "I need a cloud archive platform," this repo is deliberately not that product.

At A Glance

If you want the shortest truthful filter before reading deeper, use this table:

What you need to know	Current answer
Primary entrypoint	`CLI quickstart`
Zero-context start	`scaffold` -> `connectors`
First success	`connectors` -> `export codex --format html` -> `publish archive-index`
First visible proof	a local HTML transcript receipt plus the tracked archive-shell proof page
What it must never be reduced to	a hosted archive platform, a generic remote transcript service, or a generic MCP product

Zero-Context First Look

If you do not have a real thread id yet, start here instead of guessing what the repo expects:

Read the local workbench shape
```
cargo run -- scaffold
```
See which transcript sources already exist
```
cargo run -- connect
```

... View full README on GitHub

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Score Breakdown

MCPpedia Score

Click each category to see evidence

28D

Last scored 3h ago

How we score →

Security

3/30

No known vulnerabilities.

○

Known CVEs — No package registry to scan

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

✓

Tool stability — Tool definitions stable

○

Dependency health — No package to analyze

✗

License — No license specified

○

Authentication — No authentication required

○

Repository — active repo

CVEs checked daily via OSV.dev. Score algorithm is open source.

Reviews

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.xiaojiou176-open/agent-exporter-mcp safe to use?: io.github.xiaojiou176-open/agent-exporter-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.xiaojiou176-open/agent-exporter-mcp?: io.github.xiaojiou176-open/agent-exporter-mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.xiaojiou176-open/agent-exporter-mcp?: io.github.xiaojiou176-open/agent-exporter-mcp is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.
Is io.github.xiaojiou176-open/agent-exporter-mcp actively maintained?: io.github.xiaojiou176-open/agent-exporter-mcp is actively maintained — last commit was 1 day ago. It has 1 GitHub stars.

Similar servers

View all →

A11y Mcp

No CVEs91A

An MCP (Model Context Protocol) server for performing accessibility audits on webpages using axe-core. Use the results in an agentic loop with your favorite AI assistants (Amp/Cline/Cursor/GH Copilot) and let them fix a11y issues for you!

2 toolsremote39157.3k/wk23d ago

Luxembourg Law MCP Server

No CVEs87A

Luxembourg legislation via MCP — full-text search across statutes and provisions

7 toolsremote11/wk4d ago

Stratum MCP Server

No CVEs87A

Structured execution for Claude Code — contracts, postconditions, gates, guardrails.

3 toolsremote36d ago

Belgian Law MCP Server

No CVEs87A

Belgian legislation via MCP — full-text search across statutes and provisions

8 toolsremote7/wk5d ago

MCP Security Weekly

Get CVE alerts and security updates for io.github.xiaojiou176-open/agent-exporter-mcp and similar servers.

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

agent-exporter

agent-exporter is an archive and governance workbench for AI agent transcripts.

Try It In 3 Steps · Zero-Context First Look · Docs Landing · Archive Shell Proof · Latest Release

Front Door Map

If you only remember four things, remember these:

Question	Short answer
What is this?	an archive and governance workbench for AI agent transcripts
What should I do first?	start with the quickstart path
What is the first visible proof?	one HTML transcript receipt plus the archive shell proof
What shape should I expect?	an inspectable archive workbench, not a hosted archive platform or generic MCP product

Product Kernel

The simplest way to understand this repo is:

It turns transcript export, archiving, retrieval, evidence, and governance into an inspectable archive workbench first, instead of pretending to be a hosted service or remote platform.

Surface Model

Primary entrypoint: CLI quickstart
Secondary Surface 1: local archive shell / reports shell
Secondary Surface 2: repo-owned integration pack
Secondary Surface 3: read-only governance MCP bridge
Secondary Surface 4: root-level MCP descriptor for registry/read-back lanes (server.json)

These surfaces can coexist, but they cannot borrow authority from each other. Secondary operator-facing surfaces must not replace the current primary front door.

Flagship Public Packet

The flagship public packet for the current stage is:

GitHub repo + CLI quickstart + archive shell proof

That does not mean the other surfaces do not matter. It means each surface must clear its own review line, instead of turning a partial secondary readiness signal into a repo-wide public-ready claim.

Front Door Today

If this is your first visit, use the repo in this order:

Start with the CLI quickstart
Then inspect the archive shell proof
Only then branch into reports shell, integration pack, or governance lanes as needed

In plain English:

The product kernel already includes evidence and governance, but the public front door still needs the quickstart path to own the first screen.

Who This Repo Is For

Use this repo if your real question sounds like one of these:

"Can I export one AI agent transcript into a local artifact I can read and keep?"
"Can I turn multiple transcript artifacts into a local archive shell instead of a hosted service?"
"Can I keep retrieval, integration evidence, and governance attached to the same local workbench?"

If your first instinct is "I need a cloud archive platform," this repo is deliberately not that product.

At A Glance

If you want the shortest truthful filter before reading deeper, use this table:

What you need to know	Current answer
Primary entrypoint	`CLI quickstart`
Zero-context start	`scaffold` -> `connectors`
First success	`connectors` -> `export codex --format html` -> `publish archive-index`
First visible proof	a local HTML transcript receipt plus the tracked archive-shell proof page
What it must never be reduced to	a hosted archive platform, a generic remote transcript service, or a generic MCP product

Zero-Context First Look

If you do not have a real thread id yet, start here instead of guessing what the repo expects:

Read the local workbench shape
```
cargo run -- scaffold
```
See which transcript sources already exist
```
cargo run -- connect
```

... View full README on GitHub