Report 01M7EVPF90D4Z2QXK3Y9QYC629 · checks-v2
Agent Context API MCP server: automated checks
What HostedMCP checked on 15 Nov 2026, 05:43 UTC. Every result links to the public source it came from, so you can check it yourself.
5 of 11 checks ran · 0 high findings · not a security audit
- Checked
- 15 Nov 2026, 05:43 UTC
- Commit
- —
- Package
- hosted endpoint
- Methodology
- checks-v2
What to fix for a higher score
2 checks can earn more points. The next scan runs within a week, or right after the repository changes.
- OpenSSF Scorecard up to +15 pts
Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions. - Remote endpoint answers the MCP handshake up to +5 pts
Serve the remote endpoint over HTTPS and make sure it answers an MCP
initializerequest, or returns 401 when sign-in is required.
Origin
15 / 15 points- PassSource repository linked and reachable10 pts
dacode-dev/agent-context-api is public and reachable
github.com/dacode-dev/agent-context-api ↗ - Not checkedPackage names this repository as its source5 pts
- Not checkedBuild provenance (Sigstore attestation)10 pts
- Pass
Practices
5 / 5 points- PassCommit or release in the last year5 pts
Last commit or release 2026-08-24
github.com/dacode-dev/agent-context-api ↗ - Not checkedOpenSSF Scorecard15 pts
How to fix: Add the OpenSSF Scorecard action (
ossf/scorecard-action) to the repository and fix the weakest checks it lists, such as branch protection, pinned dependencies and token permissions.
Supply chain
not checked- Not checkedPackage name not close to a popular package10 pts
- Not checkedNo critical advisory in the package or its dependencies15 pts
Tool safety
15 / 15 points- PassNo hidden instructions to the model15 pts
0 tool descriptions and the README read; no override phrases, credential paths or hidden characters
- Not checkedDestructive tools are labelled5 pts
Endpoint
0 / 5 points- FindingRemote endpoint answers the MCP handshake5 pts
Endpoint did not answer initialize: HTTP 404
How to fix: Serve the remote endpoint over HTTPS and make sure it answers an MCP
initializerequest, or returns 401 when sign-in is required.
What these checks do not cover
- The server's code is not run and its logic is not audited.
- Results describe the repository and package on the date above; a later release can differ.
- A pass is not a guarantee of safety. Give every server the narrowest token or role it needs.