MCP servers › io.github.verifiedstate › verifiedstate-mcp
MCP server · registry snapshot 2026-10-04
io.github.verifiedstate/verifiedstate-mcp
Verified memory for AI agents. Signed assertions, billing attestation, session continuity. — the publisher's description
Summary
io.github.verifiedstate/verifiedstate-mcp is a remote MCP server listed in the official MCP registry at version 1.1.0. We have not tested it. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Repository
- link does not open publicly
- Topic
- ai-and-mlAI-classified
- Last tested
- not tested
Worth knowing before you connect it
- The linked repository does not open publicly, so the code cannot be reviewed through it.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Registry data
- snapshot 2026-10-04
- Package and repository
- checked 2026-10-06
Security testing
Has it been tested?
Feature #1It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Required input the publisher declares: Authorization (secret).
What it is
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/verifiedstate/verified-memory | Does not open (not found or private) | differs | api.github.com · 2026-10-06 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.verifiedstate
- Repository
- github.com/verifiedstate/verified-memory — does not open publicly
Source: the registry entry and api.github.com · 2026-10-06.
Choosing
Common questions about io.github.verifiedstate/verifiedstate-mcp
Answered from the data aboveHas io.github.verifiedstate/verifiedstate-mcp been security tested?
Not yet. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.
Where is the source code of io.github.verifiedstate/verifiedstate-mcp?
The registry links to github.com/verifiedstate/verified-memory, but that link does not open publicly, so the code cannot be inspected through it.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.verifiedstate/verifiedstate-mcp: MCP server record.” Data checked 2026-10-06. https://protocolprobe.com/mcp/servers/io.github.verifiedstate/verifiedstate-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can authorize a full test.
Write to hello@protocolprobe.com · corrections log · methodology