io.github.mikerawsonnz/llm-observability-orchestration
REMOTE · LANGCHAIN-CORE-LANGSMITH-OPENAI-8C02F9.GETVDA.AI · SCANNED SEP 20
Run a prompt through a LangChain (system + human) chain over Gemini on Vertex AI; optional LangSmith
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 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 139 tokens (~69/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
How do I install the io.github.mikerawsonnz/llm-observability-orchestration MCP server?
io.github.mikerawsonnz/llm-observability-orchestration is a hosted endpoint at https://langchain-core-langsmith-openai-8c02f9.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 · langchain-core-langsmith-openai-8c02f9.getvda.ai
claude mcp add --transport http mikerawsonnz-llm-observability-orchestration 'https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp'
{
"mcpServers": {
"mikerawsonnz-llm-observability-orchestration": {
"url": "https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp"
}
}
} {
"servers": {
"mikerawsonnz-llm-observability-orchestration": {
"type": "http",
"url": "https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp"
}
}
} [mcp_servers.mikerawsonnz-llm-observability-orchestration] url = "https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mikerawsonnz-llm-observability-orchestration": {
"type": "remote",
"url": "https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp",
"enabled": true
}
}
} openclaw mcp add mikerawsonnz-llm-observability-orchestration --url 'https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp' --transport streamable-http
mcp_servers:
mikerawsonnz-llm-observability-orchestration:
url: "https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp" {
"McpServers": {
"mikerawsonnz-llm-observability-orchestration": {
"Transport": "http",
"Url": "https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp"
}
}
} assistant mcp add mikerawsonnz-llm-observability-orchestration -t streamable-http -u 'https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp'
{
"mcpServers": {
"mikerawsonnz-llm-observability-orchestration": {
"type": "http",
"url": "https://langchain-core-langsmith-openai-8c02f9.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.
- 26 Aug 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 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 2 Aug 26 0
- Schema quality: 55 → 69 ▼ functional
- Schema quality: poor → fair functional
- New tool “selftest” functional
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
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://langchain-core-langsmith-openai-8c02f9.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=langchain-core-langsmith-openai-8c02f9.getvda.ai | CN=WR3,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 438bbe43e0aa9cb60add20f0d585242a |
| SANs: langchain-core-langsmith-openai-8c02f9.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 langchain-core-langsmith-openai-8c02f9.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://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp | Verified | 200 | |
| http (plaintext) | http://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp | HTTPS enforced | 302 | https://langchain-core-langsmith-openai-8c02f9.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 ~55
Run a prompt through a LangChain (system + human) chain over Gemini on Vertex AI; optional LangSmith tracing.
| 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.
What is the io.github.mikerawsonnz/llm-observability-orchestration MCP server?
io.github.mikerawsonnz/llm-observability-orchestration is an MCP server listed in the public MCP registry as io.github.mikerawsonnz/llm-observability-orchestration. Run a prompt through a LangChain (system + human) chain over Gemini on Vertex AI; optional LangSmith. This page covers its hosted endpoint (https://langchain-core-langsmith-openai-8c02f9.getvda.ai/mcp).
Is the io.github.mikerawsonnz/llm-observability-orchestration MCP server safe to use?
io.github.mikerawsonnz/llm-observability-orchestration 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 io.github.mikerawsonnz/llm-observability-orchestration MCP server expose?
io.github.mikerawsonnz/llm-observability-orchestration exposes 2 tools: invoke, selftest. Their descriptions and schemas cost roughly 139 tokens of context every time the server is loaded.
Does the io.github.mikerawsonnz/llm-observability-orchestration MCP server require authentication?
No. We connected to io.github.mikerawsonnz/llm-observability-orchestration without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.mikerawsonnz/llm-observability-orchestration MCP server still maintained?
io.github.mikerawsonnz/llm-observability-orchestration 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.