
MCP Verify
io.sentinelsignalPublished by sentinelsignal.ioOfficial publisherv1.0.269Updated Oct 25, 2026
Trust, freshness, policy, and discovery layer for public MCP servers.
The publisher's own server: Scoring
Overview
A remote MCP endpoint that acts as a trust, freshness, policy and discovery layer for public MCP servers.
- What you can do
- The manifest lists no tools, so the exact operations are not documented. Based on the registry description, it is positioned as a trust, freshness, policy and discovery layer for public MCP servers, suggesting an assistant could look up and assess other public MCP servers. No further capability details are provided in the available material.
- When to use it
- Consider it when you want an assistant to discover public MCP servers or check their trust, freshness or policy standing before relying on them. Without tool listings or documentation, confirm its actual behavior before depending on it.
- Requirements
- It runs as a remote streamable HTTP endpoint at the provider's hosted address; no local runtime, packages, environment variables or headers are declared. The manifest declares no authentication, though the provider may still require it in practice.
Installation
In SourceWeft
- Open MCP Verify in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.sentinelsignal%2Fverify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"verify": {
"type": "http",
"url": "https://verify.sentinelsignal.io/mcp"
}
}
}Tools
0Version history
1- v1.0.269LatestSep 16, 2026
Score
28% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.