AskAgent
REMOTE · ASKAGENT.DEV · SCANNED SEP 25
Archive of verbatim errors with root causes and fixes that AI agents search by exact error string.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 304 tokens (~101/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the AskAgent MCP server?
AskAgent is a hosted endpoint at https://askagent.dev/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 · askagent.dev
claude mcp add --transport http singularitystudiosdev-askagent 'https://askagent.dev/mcp'
{
"mcpServers": {
"singularitystudiosdev-askagent": {
"url": "https://askagent.dev/mcp"
}
}
} {
"servers": {
"singularitystudiosdev-askagent": {
"type": "http",
"url": "https://askagent.dev/mcp"
}
}
} [mcp_servers.singularitystudiosdev-askagent] url = "https://askagent.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"singularitystudiosdev-askagent": {
"type": "remote",
"url": "https://askagent.dev/mcp",
"enabled": true
}
}
} openclaw mcp add singularitystudiosdev-askagent --url 'https://askagent.dev/mcp' --transport streamable-http
mcp_servers:
singularitystudiosdev-askagent:
url: "https://askagent.dev/mcp" {
"McpServers": {
"singularitystudiosdev-askagent": {
"Transport": "http",
"Url": "https://askagent.dev/mcp"
}
}
} assistant mcp add singularitystudiosdev-askagent -t streamable-http -u 'https://askagent.dev/mcp'
{
"mcpServers": {
"singularitystudiosdev-askagent": {
"type": "http",
"url": "https://askagent.dev/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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Probed https://askagent.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=askagent.dev | CN=WE1,O=Google Trust Services,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2737f52272d254211368f8709a817e3b |
| SANs: askagent.dev, *.askagent.dev | ||||||
| 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 askagent.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| askagent.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://askagent.dev/mcp | Verified | 200 | |
| http (plaintext) | http://askagent.dev/mcp | HTTPS enforced | 308 | https://askagent.dev/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 →
get_fix ~113
Read one AskAgent fix by slug (get slugs from search_fixes). Always returns the free layer: verbatim error, full diagnosis, language, tags. With a member Bearer API token (scope read:full) the response also carries body_md, the complete fix. Without auth it returns the free layer plus a paywall pointer — the fix is one call once you are a member.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Post slug, e.g. "postgres-rls-new-row-violates-policy" |
No output schema declared.
No examples provided.
list_samples ~42
List the 3 complete sample fixes of AskAgent — readable in full (body_md included) with no account, so you can judge archive quality before becoming a member.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_fixes ~91
Search the AskAgent archive of real, working fixes by error string. Paste the exact error from a stack trace or log (symptom words also work). Returns match count with each match's title, slug, language and free diagnosis. Call this on every unexplained error before debugging from scratch.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The error string or symptom, e.g. "RangeError: Invalid time value" |
No output schema declared.
No examples provided.
What is the AskAgent MCP server?
AskAgent is an MCP server listed in the public MCP registry as io.github.singularitystudiosdev/askagent. Archive of verbatim errors with root causes and fixes that AI agents search by exact error string. This page covers its hosted endpoint (https://askagent.dev/mcp).
Is the AskAgent MCP server safe to use?
AskAgent scores 73 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 AskAgent MCP server expose?
AskAgent exposes 3 tools: search_fixes, get_fix, list_samples. Their descriptions and schemas cost roughly 246 tokens of context every time the server is loaded.
Does the AskAgent MCP server require authentication?
No. We connected to AskAgent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AskAgent MCP server still maintained?
AskAgent is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.