Singularity - MCP Discovery & Security Gateway
REMOTE · SINGULARITY-OSD2.ONRENDER.COM · SCANNED SEP 20
Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Singularity - MCP Discovery & Security Gateway server?
Singularity - MCP Discovery & Security Gateway is a hosted endpoint at https://singularity-osd2.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · singularity-osd2.onrender.com
claude mcp add --transport http gaurav-kumar-sinha-060705-singularity 'https://singularity-osd2.onrender.com/mcp'
{
"mcpServers": {
"gaurav-kumar-sinha-060705-singularity": {
"url": "https://singularity-osd2.onrender.com/mcp"
}
}
} {
"servers": {
"gaurav-kumar-sinha-060705-singularity": {
"type": "http",
"url": "https://singularity-osd2.onrender.com/mcp"
}
}
} [mcp_servers.gaurav-kumar-sinha-060705-singularity] url = "https://singularity-osd2.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gaurav-kumar-sinha-060705-singularity": {
"type": "remote",
"url": "https://singularity-osd2.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add gaurav-kumar-sinha-060705-singularity --url 'https://singularity-osd2.onrender.com/mcp' --transport streamable-http
mcp_servers:
gaurav-kumar-sinha-060705-singularity:
url: "https://singularity-osd2.onrender.com/mcp" {
"McpServers": {
"gaurav-kumar-sinha-060705-singularity": {
"Transport": "http",
"Url": "https://singularity-osd2.onrender.com/mcp"
}
}
} assistant mcp add gaurav-kumar-sinha-060705-singularity -t streamable-http -u 'https://singularity-osd2.onrender.com/mcp'
{
"mcpServers": {
"gaurav-kumar-sinha-060705-singularity": {
"type": "http",
"url": "https://singularity-osd2.onrender.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 −29
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Sept 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://singularity-osd2.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 756bcb97dcf1455f0ebf70e5dbe07256 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of singularity-osd2.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://singularity-osd2.onrender.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://singularity-osd2.onrender.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://singularity-osd2.onrender.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://singularity-osd2.onrender.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://singularity-osd2.onrender.com/mcp |
| Authorisation server | https://singularity-osd2.onrender.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://singularity-osd2.onrender.com/mcp | Auth required | 401 | |
| http (plaintext) | http://singularity-osd2.onrender.com/mcp | HTTPS enforced | 301 | https://singularity-osd2.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_tools ~69
Compare several indexed tools side by side on trust signals: trust score, security flags, publisher verification, category, and pricing tier. Pass 2-6 slugs. Fit depends on the specific problem - call find_solutions for ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | Tool slugs to compare. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
find_solutions ~113
Given a user's problem in natural language, return ranked solution recommendations (software platforms and MCP-connectable tools). Each result includes a semantic fit score, a trust/security score, any security flags, and a short rationale. Surface the flags to the user transparently.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pricing_tier | – | – | Optional ceiling: free, freemium, paid, or enterprise. |
| problem | string | yes | The user's problem or need, in their own words. |
| top_k | integer | – | How many recommendations to return. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_trust_report ~72
Get a detailed trust and security report for one indexed tool by slug: publisher verification, permissions requested vs actually needed (with the overreach highlighted), injection-scan verdicts on the tool description, and the trust score interpretation.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tool slug, e.g. 'github-mcp'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Singularity - MCP Discovery & Security Gateway server?
Singularity - MCP Discovery & Security Gateway is listed in the public MCP registry as io.github.gaurav-kumar-sinha-060705/singularity. Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring. This page covers its hosted endpoint (https://singularity-osd2.onrender.com/mcp).
Is the Singularity - MCP Discovery & Security Gateway server safe to use?
Singularity - MCP Discovery & Security Gateway scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Singularity - MCP Discovery & Security Gateway server expose?
Singularity - MCP Discovery & Security Gateway exposes 3 tools: find_solutions, get_trust_report, compare_tools. Their descriptions and schemas cost roughly 254 tokens of context every time the server is loaded.
Does the Singularity - MCP Discovery & Security Gateway server require authentication?
Yes. Singularity - MCP Discovery & Security Gateway asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Singularity - MCP Discovery & Security Gateway server still maintained?
Singularity - MCP Discovery & Security Gateway is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.