ai.getvda/integration-agent
REMOTE · DRIFT.GETVDA.AI · SCANNED SEP 25
Integration Agent
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 6 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 357 tokens (~59/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the ai.getvda/integration-agent MCP server?
ai.getvda/integration-agent is a hosted endpoint at https://drift.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 · drift.getvda.ai
claude mcp add --transport http ai-getvda-integration-agent 'https://drift.getvda.ai/mcp'
{
"mcpServers": {
"ai-getvda-integration-agent": {
"url": "https://drift.getvda.ai/mcp"
}
}
} {
"servers": {
"ai-getvda-integration-agent": {
"type": "http",
"url": "https://drift.getvda.ai/mcp"
}
}
} [mcp_servers.ai-getvda-integration-agent] url = "https://drift.getvda.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-getvda-integration-agent": {
"type": "remote",
"url": "https://drift.getvda.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-getvda-integration-agent --url 'https://drift.getvda.ai/mcp' --transport streamable-http
mcp_servers:
ai-getvda-integration-agent:
url: "https://drift.getvda.ai/mcp" {
"McpServers": {
"ai-getvda-integration-agent": {
"Transport": "http",
"Url": "https://drift.getvda.ai/mcp"
}
}
} assistant mcp add ai-getvda-integration-agent -t streamable-http -u 'https://drift.getvda.ai/mcp'
{
"mcpServers": {
"ai-getvda-integration-agent": {
"type": "http",
"url": "https://drift.getvda.ai/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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 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.
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://drift.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=drift.getvda.ai | CN=WR3,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | RSA 2048 | SHA256-RSA | ec1641cf62660574101fba4037f18698 |
| SANs: drift.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 drift.getvda.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| getvda.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://drift.getvda.ai/mcp | Verified | 200 | |
| http (plaintext) | http://drift.getvda.ai/mcp | HTTPS enforced | 302 | https://drift.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 →
drift_check ~61
FREE. Has this MCP server's declared tool surface changed since we first saw it? Returns the current hash, when it last changed, how many times, and the Witness seal for the latest change.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | the server's MCP endpoint URL |
No output schema declared.
No examples provided.
drift_diff ~53
What actually changed: field-level detail for this server's observed changes, including which tool moved and whether the change touched a description, a schema or an annotation.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | the server's MCP endpoint URL |
No output schema declared.
No examples provided.
drift_hash ~60
FREE. Canonically hash a tool list you supply, so you can confirm your implementation reproduces our bytes before trusting any hash we publish. ensure_ascii=False is the flag people miss.
| Name | Type | Req | Description |
|---|---|---|---|
| tools | array | yes | MCP tool objects as returned by tools/list |
No output schema declared.
No examples provided.
drift_probe ~48
Fetch this server RIGHT NOW and compare it to our stored baseline. Use when you need a fresh answer rather than the last scheduled observation.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | the server's MCP endpoint URL |
No output schema declared.
No examples provided.
drift_status ~51
FREE. Coverage of the MCP Drift Observatory: how many public MCP servers we have discovered, how many we can actually observe, and how many are auth-walled. Reports the denominator, not just the flattering numerator.
Input schema present but exposes no named parameters.
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.
What is the ai.getvda/integration-agent MCP server?
ai.getvda/integration-agent is an MCP server listed in the public MCP registry as ai.getvda/integration-agent. Integration Agent. This page covers its hosted endpoint (https://drift.getvda.ai/mcp).
Is the ai.getvda/integration-agent MCP server safe to use?
ai.getvda/integration-agent scores 76 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/integration-agent MCP server expose?
ai.getvda/integration-agent exposes 6 tools: drift_status, drift_hash, drift_check, drift_diff, drift_probe, selftest. Their descriptions and schemas cost roughly 357 tokens of context every time the server is loaded.
Does the ai.getvda/integration-agent MCP server require authentication?
No. We connected to ai.getvda/integration-agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.getvda/integration-agent MCP server still maintained?
ai.getvda/integration-agent 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.