Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aguasto Research

REMOTE · WWW.AGUASTO.COM

Search Aguasto's published research descriptions and canonical references.

Available components

+3 this week 75 Trust /100

Last scanned (23 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 4 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2169 tokens (~23/item across 92 items; 2 tools + 90 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Resource “Developers & Agent Access” was removed ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New resource “API Versioning & Deprecation Policy” functional
    • New resource “Developer API, MCP & SDK Documentation” functional
    • New resource “Developer Sandbox & Synthetic API Tests” functional
    • New resource “Public Research Terms of Use” functional
  • 27 Oct 26 72

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Probed https://www.aguasto.com/mcp/docs

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.aguasto.com CN=YR1,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 RSA 2048 SHA256-RSA 6fe28b1f8c7f5badc508dd7ffc26ad5480e
SANs: www.aguasto.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.aguasto.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aguasto.com. 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
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.aguasto.com/mcp/docs Verified 200
http (plaintext) http://www.aguasto.com/mcp/docs HTTPS enforced 308 https://www.aguasto.com/mcp/docs
MCP tools · 2 exposed · ~90 tokens

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 →

Tool Tokens
get_page ~48

Retrieve a published page's description, date, canonical URL and Markdown link. Not the full article text.

NameTypeReqDescription
pathstringyesExact published path, such as /gpus or /company.

No output schema declared.

No examples provided.

search_pages ~42

Find published Aguasto page titles, descriptions and canonical references. Follow the page for full sourced evidence.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Aguasto Research MCP server?

Aguasto Research is a hosted endpoint at https://www.aguasto.com/mcp/docs, 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 · www.aguasto.com

# add to Claude Code
claude mcp add --transport http com-aguasto-www-docs 'https://www.aguasto.com/mcp/docs'
Common questions

What is the Aguasto Research MCP server?

Aguasto Research is an MCP server listed in the public MCP registry as com.aguasto.www/docs. Search Aguasto's published research descriptions and canonical references. This page covers its hosted endpoint (https://www.aguasto.com/mcp/docs).

Is the Aguasto Research MCP server safe to use?

Aguasto Research scores 75 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 Aguasto Research MCP server expose?

Aguasto Research exposes 2 tools: search_pages, get_page. Their descriptions and schemas cost roughly 90 tokens of context every time the server is loaded.

Does the Aguasto Research MCP server require authentication?

No. We connected to Aguasto Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Aguasto Research MCP server still maintained?

Aguasto Research is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.