Everything MCP server. What it holds.
No credential, no file access, no outbound requests. The risk is in what the agent does with the output, not in the server. Published by MCP reference server.
The record
Taken from the official documentation linked at the bottom.
| Field | Value |
|---|---|
| Publisher | MCP reference server |
| Authentication | None. |
| What it holds | Nothing. It is a reference and test server that exercises the protocol. |
| What that reaches | Nothing outside itself. |
| Risk class | Holds nothing No credential, no file access, no outbound requests. The risk is in what the agent does with the output, not in the server. |
Why it matters
Worth an entry only to say that it belongs in development and not in a configuration that ships. A test server left in a config is a reminder that nobody reviewed the config.
Not whether the server is trustworthy. What it holds, and what that reaches.
What to check
Whether it appears in any configuration outside a development machine.
The same questions apply to any server in this database, which is why the MCP server security page is the general version of this page.
Holds nothing
Where this comes from.
Every field above is taken from the official documentation. Where it does not say, this page does not either.
Questions, answered.
The two questions this record answers.
What credential does the Everything MCP server hold?
Nothing. It is a reference and test server that exercises the protocol.
What can it reach?
Nothing outside itself.
See what your agents can reach. Before someone else does.
Book a demo and we walk through the access paths in an environment like yours.