noelschwarz/copper
Copper is an open-source CLI by Basematter that tails MCP (Model Context Protocol) tool calls, redacts secrets, and flags risky ones. See what your AI agent is actually doing.
Production readiness
Evidence confidence
Recommended for
Client readiness verdicts
Evidence provenance
initialize• Missingtools_list• Missingtransport_compliance_probe• Missingstep_up_auth_probe• Missingconnector_replay_probe• Missing — Frozen tool snapshots must survive refresh.request_association_probe• Missing — Roots, sampling, and elicitation should stay request-scoped.
Evidence provenance
initialize• Missingtools_list• Missingtransport_compliance_probe• Missing
Evidence provenance
action_safety_probe• Missing
Evidence provenance
tool_snapshot_probe• Missingconnector_replay_probe• Missing
Why not ready by client
Remediation checklist
- No explicit blockers recorded.
Remediation checklist
- No explicit blockers recorded.
Remediation checklist
- No explicit blockers recorded.
Verdict traces
never_validated• high • Server has never been validated
Client verdict trace table
| Verdict | Status | Checks | Winning source | Conflicts |
|---|---|---|---|---|
openai_connectors |
Blocked | initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe | live_validation | none |
claude_desktop |
Blocked | initialize, tools_list, transport_compliance_probe | live_validation | none |
unsafe_for_write_actions |
Yes | action_safety_probe | live_validation | none |
snapshot_churn_risk |
Low | tool_snapshot_probe, connector_replay_probe | history | none |
Publishability policy profiles
- Search Fetch Only: No
- Write Actions Present: No
- Oauth Configured: No
- Admin Refresh Required: No
- Safe For Company Knowledge: No
- Safe For Messages Api Remote Mcp: No
- Search Fetch Only: No
- Write Actions Present: No
- Oauth Configured: No
- Admin Refresh Required: No
- Safe For Company Knowledge: No
- Safe For Messages Api Remote Mcp: No
Compatibility fixtures
- remote_http_endpoint: Likely to fail
- oauth_discovery: Degraded
- frozen_tool_snapshot_refresh: Passes
- request_association: Passes
- remote_transport: Likely to fail
- tool_discovery: Likely to fail
- auth_connect: Likely to fail
- safe_write_review: Degraded
Authenticated validation sessions
/v1/verify/v1/ci/previewPublic server reputation
Incident & change feed
No incidents or changes recorded yet.
Capabilities
- OAuth:
- DCR/CIMD:
- Prompts:
- Homepage: https://basematter.dev
- Docs: https://basematter.dev
- Support: https://github.com/noelschwarz/copper
- Icon: https://avatars.githubusercontent.com/u/139234123?v=4
- Remote endpoint: none
- Server card: none
Security posture
Tool capability & risk inventory
No tool inventory available from the latest validation run.
Write-action governance
Status detail: No write-action governance evidence is available yet.
| Tool | Risk | Flags | Safeguards |
|---|---|---|---|
| No high-risk tools were detected on the latest run. | |||
Action-controls diff
Need at least two validation runs before diffing action controls.
Why this score?
Algorithmic score breakdown
No score components recorded yet.
Compatibility profiles
Connector URL: https://example.com/mcp # No OAuth metadata detected. # Server: github-noelschwarz/copper
{
"mcpServers": {
"copper": {
"command": "npx",
"args": ["mcp-remote", "https://example.com/mcp"]
}
}
}
smithery mcp add "https://example.com/mcp"
curl -sS https://example.com/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Actionable remediation
| Severity | Remediation | Why it matters | Recommended action |
|---|---|---|---|
| High | Respond to server has never been validated | No live validation evidence exists yet for this entry. | Inspect the latest validation evidence and resolve the client-visible regression.Playbook
|
| Medium | Raise Access & Protocol score | Connectivity, auth, and transport expectations for common clients. | Tighten auth discovery, session behavior, and transport metadata until remote clients can connect without guesswork.Playbook
|
| Medium | Raise Adoption & Market score | Adoption clues and public evidence that the server is intended for external use. | Increase external documentation and directory coverage so users can discover and evaluate the server.Playbook
|
| Medium | Raise Discovery & Governance score | How well the server is documented, listed, and governed in public registries. | Fill out homepage, docs, support, license, and registry metadata so directories stay aligned.Playbook
|
| Medium | Raise Interface Quality score | How well the tool/resource interface communicates and behaves under automation. | Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.Playbook
|
| Medium | Raise Reliability & Trust score | Operational stability, consistency, and trustworthiness over time. | Stabilize behavior over time and reduce failure drift between validation runs.Playbook
|
| Medium | Raise Security Posture score | How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs. | Reduce destructive, egress, exec, secret, and freeform-input risk across the exposed tool surface.Playbook
|
Point loss breakdown
No current score penalties are recorded.
Validation diff
Need at least two validation runs before diffing changes.
Tool snapshot diff & changelog
Need at least two validation runs before building a tool changelog.
Connector replay
Required-argument replay breaks
| Tool | Added required args | Removed required args |
|---|---|---|
| No required-argument replay breaks detected. | ||
Output-schema replay breaks
| Tool | Removed properties | Added properties |
|---|---|---|
| No output-schema replay breaks detected. | ||
Transport compliance drilldown
Issues: none
Request association
Utility coverage
Benchmark tasks
| Benchmark task | Status | Evidence |
|---|---|---|
| Discover tools | Likely to fail |
|
| Read-only fetch flow | Likely to fail |
|
| OAuth-required connect | Degraded |
|
| Safe write flow with confirmation | Likely to fail |
|
Registry & provenance divergence
| Field | Registry | Live server card |
|---|---|---|
| Title | n/a | n/a |
| Version | n/a | n/a |
| Homepage | n/a | n/a |
Active alerts
- Server has never been validated (high)
No live validation evidence exists yet for this entry.
Aliases & registry graph
| Identifier | Source | Canonical | Score |
|---|---|---|---|
github-noelschwarz/copper |
github_topic_registry | yes | n/a |
Alias consolidation
Source disagreements
| Field | What differs | Observed values |
|---|---|---|
| No source disagreements detected. | ||
Install snippets
Connector URL: https://example.com/mcp # No OAuth metadata detected. # Server: github-noelschwarz/copper
{
"mcpServers": {
"copper": {
"command": "npx",
"args": ["mcp-remote", "https://example.com/mcp"]
}
}
}
smithery mcp add "https://example.com/mcp"
curl -sS https://example.com/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Agent access & tool surface
tools/list, prompts/list, and resources/list checks.github-noelschwarz/copper.Claims & monitoring
No verified maintainer claim recorded.
Alert routing
| Watch | Team | Channels | Minimum severity |
|---|---|---|---|
| No active watch destinations. | |||
Maintainer analytics
Maintainer response quality
Maintainer annotations
No maintainer annotations have been recorded yet.
Maintainer rebuttals & expected behavior
No maintainer rebuttals or expected-behavior overrides are recorded yet.
Latest validation evidence
No validation run available yet.
Raw evidence view
Show raw JSON evidence
{
"checks": {},
"failures": {},
"remote_url": null,
"server_card_payload": null,
"server_identifier": "github-noelschwarz/copper"
}
Known versions
- No versions recorded.
Validation history
| Timestamp | Status | Score | Latency | Tools |
|---|---|---|---|---|
| Not enough history for trend points yet. | ||||
Validation timeline
No validation timeline is available yet.
Recent validation runs
| Started | Status | Summary | Latency | Checks |
|---|---|---|---|---|
| No validation runs yet. | ||||