Socket MCP (official, remote)
Capped at 80: 1 of 3 real tool calls passed in our test; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 80 because not every real tool call passed. Not a quality or security rating. Why scores are capped
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested Socket's hosted MCP at https://mcp.socket.dev/ (server socket 0.3.0; source SocketDev/socket-mcp, MIT, 141 GitHub stars when checked). Initialize and tools/list worked with no account (7 tools). Of 3 real calls, depscore for npm lodash 4.17.20 returned license, maintenance, quality, supply-chain and vulnerability scores. package_files and organizations answered 'Authentication required for this tool', so those need a Socket sign-in (OAuth). Core tools not tested beyond depscore.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): partial. 1 of 3 read calls passed anonymously; the other 2 need a Socket sign-in. Evidence: live endpoint probe, Nov 11, 2026.
Transport (tested 2026-11-11): Streamable HTTP
Token cost (estimate): approx. 2049 tokens, cl100k estimate (7 tools, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 7 read, 0 write (state-changing), 0 unclassified · Auth: OAuth · Rate limit: unknown · Pricing unit: unknown
Auth: OAuth. Rate limit: unknown. Pricing unit: unknown.
alerts— readdepscore— readorganizations— readpackage_file_contents— readpackage_file_grep— readpackage_files— readthreat_feed— read
live endpoint probe, Nov 11, 2026: package_files and organizations answered 'Authentication required for this tool'; SocketDev/socket-mcp README (quote in live endpoint probe, Nov 11, 2026): 'Connect your MCP client to the hosted server at https://mcp.socket.dev/ and authenticate through OAuth'
Score 80/100 · Tools 7 · Token cost approx. 2,049 tokens · Compare · Last tested 2026-11-11 · Server version 0.3.0 · Remote endpoint https://mcp.socket.dev/ (streamable-http) · Repo SocketDev/socket-mcp
Summary: Socket MCP (official, remote) completed an MCP handshake without credentials and exposed 7 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 7
- Context cost
- approx. 2049 tokens, cl100k estimate (7 tools, measured 2026-11-11; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-11
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://mcp.socket.dev/ reachable over streamable-http (HTTP 200) in 0.7s; no install step for remote servers. |
| handshake | pass | 30 | MCP initialize (protocol 2025-06-18, server socket 0.3.0) + tools/list over streamable-http succeeded with no credentials; 7 tools listed in 0.7s. Tool calls may still need a key. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 141 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (vendor repo README (github.com/SocketDev/socket-mcp)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 2049 tokens, cl100k estimate for 7 tools · about 25% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-11
- Install from the registry (remote endpoint: connection only)
- We connected with no credentials and asked for its tool list: it listed 7 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not checked (remote-only): hosted endpoint, version unknown.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-11 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
3400cc534b21: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "socket-remote",
"version": null,
"registry": "remote",
"status": "working",
"tested": "2026-11-11",
"tools_count": 7,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"Endpoint https://mcp.socket.dev/ reachable over streamable-http (HTTP 200) in 0.7s; no install step for remote servers."
],
"handshake": [
"pass",
30,
"MCP `initialize` (protocol 2025-06-18, server socket 0.3.0) + `tools/list` over streamable-http succeeded with no credentials; 7 tools listed in 0.7s. Tool calls may still need a key."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 141 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (vendor repo README (github.com/SocketDev/socket-mcp))."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
https://mcp.socket.dev/
Tools listed
alerts, depscore, organizations, package_file_contents, package_file_grep, package_files, threat_feed
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"socket-mcp-remote": {
"type": "http",
"url": "https://mcp.socket.dev/"
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. No install step: it is a remote server at https://mcp.socket.dev/.
- Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (7 in our test).
{
"mcpServers": {
"socket-mcp-remote": {
"type": "http",
"url": "https://mcp.socket.dev/"
}
}
}Test history
- 2026-11-11: Permission card updated
- 2026-11-11: New
FAQ
Is Socket MCP deprecated?
No. socket-remote was not deprecated or archived when we last tested it on 2026-11-11.
What replaces Socket MCP?
Nothing; Socket MCP (official, remote) is not deprecated as of 2026-11-11.
Does Socket MCP need an API key?
It connects and lists 7 tools without a key, but its tool calls need one.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.