Connect agents to GitHub repositories, issues, pull requests, and code search.
Context7 MCP
Fetch current library documentation and examples directly into coding agents.
A curated public baseline; every entry carries a verification level and risk labels. 25 from the automated pipeline
What it is good for
Fetch current library documentation and examples directly into coding agents. AgentMaps treats this as a mcp server candidate and scores it with a capped benchmark score plus a separate recommendation score that includes trust, platform fit, setup preference, and risk preference.
Use cases
- - Review code changes
- - Inspect repository context
- - Generate implementation notes
- - Gather sources
- - Compare claims
Best for
- - Developers using Cursor for coding workflows.
- - Teams that want visible setup, verification, and risk evidence before adoption.
Not for
- - Users expecting a fully managed marketplace install flow.
- - Users who need enterprise SSO controls.
Limitations
- - Scenario-level L5-L7 benchmark testing is not part of the current MVP record.
Runtime pattern before adoption
This behaves like a tool connector; the user still decides when to authorize calls, what context to pass, and how to roll back.
Visible states
- Collect task context and platform constraints
- Preview setup, source, and permission boundaries
- Trial in a sandbox or low-permission environment
- Record trial result before team adoption
User controls
- Revise task/platform filters
- Add to Compare
- Open source for review
- Cancel high-risk adoption
- Submit pending/staging evidence
Approval gates
- External network target approval
Failure recovery
- On trial failure, fall back to source docs, alternatives, or pending/staging evidence submission.
Trial acceptance
- Can a user find a task-fit candidate within two minutes
- Can the UI explain why it is recommended and where it does not fit
- Can the user identify token, write, shell, network, or local file risk
- Can the user separate L1/L2 evidence from full runtime proof
- Does a failed trial have fallback or manual takeover
Verification evidence
The matrix shows passed, partial, skipped, and not-tested boundaries. It is not production adoption approval.
Source, docs, license, or package metadata exists.
Static review assigns permission and risk boundaries.
Install path can be checked, but not necessarily in your environment.
Interface or entrypoint parsed; not a production safety approval.
- Seed profile normalized into AgentMaps schema.
- Source and documentation fields are present.
- Static risk flags are assigned.
- Install path is represented for harness checks.
- Interface metadata is represented for parser checks.
- Benchmark score capped at 88 by L4 verification.
Trust profile
Risk findings
- - External Network
Verified evidence
- - Seed profile normalized into AgentMaps schema.
- - Source and documentation fields are present.
- - Static risk flags are assigned.
- - Install path is represented for harness checks.
Score breakdown
Why it scores well
- - Clear task fit for the selected scenario.
- - Static verification evidence is available.
- - Portable across multiple AI clients.
Watch outs
- - Scenario testing is still pending.
- - Production adoption still needs local validation.
Alternatives
Give agents controlled access to Supabase projects, schemas, SQL, and project metadata.
Expose selected local directories to agents for read and write file workflows.