ai.getvda/multi-provider-schema-output-agent
REMOTE · INSTRUCTOR-LITELLM-6AF681.GETVDA.AI
Multi-Provider Schema Output Agent
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 2 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 140 tokens (~70/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 3 Oct 26 78
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Sept 26 0
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 5 Nov 2026 · Probed https://instructor-litellm-6af681.getvda.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=instructor-litellm-6af681.getvda.ai | CN=WR3,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | RSA 2048 | SHA256-RSA | 99dc9c3e640213f09eba6f75edc63d9 |
| SANs: instructor-litellm-6af681.getvda.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of instructor-litellm-6af681.getvda.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| getvda.ai. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://instructor-litellm-6af681.getvda.ai/mcp | Verified | 200 | |
| http (plaintext) | http://instructor-litellm-6af681.getvda.ai/mcp | HTTPS enforced | 302 | https://instructor-litellm-6af681.getvda.ai/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 →
invoke ~56
Turn a prompt + a field schema into validated, typed JSON (Instructor over Gemini 2.5 Flash on Vertex AI).
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | JSON request for this capability (the same body you'd send as an A2A message). |
No output schema declared.
No examples provided.
selftest ~84
FREE, no payment required. Runs this agent's real capability on a fixed canned input and returns the genuine result, an honest assertion grade, and the full trust manifest (signed Agent Card, JWKS, governance/licence chain, safety posture) with a proof link for every claim. Intended for registries, graders and auditors: this is behavioural evidence, not a self-description.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ai.getvda/multi-provider-schema-output-agent MCP server?
ai.getvda/multi-provider-schema-output-agent is a hosted endpoint at https://instructor-litellm-6af681.getvda.ai/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 · instructor-litellm-6af681.getvda.ai
claude mcp add --transport http ai-getvda-multi-provider-schema-output-agent 'https://instructor-litellm-6af681.getvda.ai/mcp'
What is the ai.getvda/multi-provider-schema-output-agent MCP server?
ai.getvda/multi-provider-schema-output-agent is an MCP server listed in the public MCP registry as ai.getvda/multi-provider-schema-output-agent. Multi-Provider Schema Output Agent. This page covers its hosted endpoint (https://instructor-litellm-6af681.getvda.ai/mcp).
Is the ai.getvda/multi-provider-schema-output-agent MCP server safe to use?
ai.getvda/multi-provider-schema-output-agent scores 78 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 ai.getvda/multi-provider-schema-output-agent MCP server expose?
ai.getvda/multi-provider-schema-output-agent exposes 2 tools: invoke, selftest. Their descriptions and schemas cost roughly 140 tokens of context every time the server is loaded.
Does the ai.getvda/multi-provider-schema-output-agent MCP server require authentication?
No. We connected to ai.getvda/multi-provider-schema-output-agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.getvda/multi-provider-schema-output-agent MCP server still maintained?
ai.getvda/multi-provider-schema-output-agent is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ai.getvda/multi-provider-schema-output-agent MCP server?
VerifyMCP ran 12 checks on ai.getvda/multi-provider-schema-output-agent, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ai.getvda/multi-provider-schema-output-agent: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.