io.github.mbeato/agentcontext

MCPcommunity
v0.1.2io.github.mbeatoUnknownUpdated 5mo agonpmGitHub

Normalize AGENTS.md / CLAUDE.md / .cursor/rules / .clinerules / .windsurf/rules from one source.

MCP server for @mbeato/agentcontext — normalize agent-context files (, , , , , , ) from any MCP-aware coding agent. — parse all detected formats in a repo, return one unified IR. — render the IR to one or more target formats; returns the file map. v0.1 — early. See for the project home.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.mbeato
LicenseUnknown
Version0.1.2
Sourcemcp-registry
npm@mbeato/agentcontext-mcp
GitHubmbeato/agentcontext-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 2 resolved · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.1.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev0.1.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

read_agent_contextNo description published

This tool published no description. Forge does not invent one.

convert_agent_contextNo description published

This tool published no description. Forge does not invent one.

0 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for @mbeato/agentcontext — normalize agent-context files (, , , , , , ) from any MCP-aware coding agent. — parse all detected formats in a repo, return one unified IR. — render the IR to one or more target formats; returns the file map. v0.1 — early. See for the project home.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

2 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.