Compatibility is inferred from published configuration rules and is not manually verified in each client.
Client setup cannot be inferred yet. This public check did not observe a complete tool contract or an authentication challenge, so there is no honest compatibility signal.
· A complete public contract was observed earlier. The latest check did not re-observe it. This is a limit of evidence, not a quality judgment.
Warning
A Watch would follow availability and the last known public contract, and alert only if a change may affect the selected client.
Evidence and limitations
Method: anonymous Streamable HTTP probe. We never invoke a tool.
Attempted protocols: 2026-07-28, 2025-11-25
ProtocolNot listed in this check
TransportHTTPS · HTTP 429
AuthNo authentication challenge in this check
EvidenceTransport only
Total latency5803 ms
Response bytes0
MCP_RESPONSE_ERROR — The endpoint returned an incomplete or incompatible MCP response.
Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
Tools and declared exposure
Server annotations are declarations, not verified behavior.
Show 3 of 3 server-provided tool definitions
enquiry_describe
No effect details providedShow server-provided details
What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)
Server description (copied; language not verified)
Read first. States plainly what submit_enquiry does on M365 Migration Cost: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
Input schema (server-provided preview — do not copy)
No effect details providedShow server-provided details
The questions the enquiry asks
Server description (copied; language not verified)
Every field of the M365 Migration Cost enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
Input schema (server-provided preview — do not copy)
No effect details providedShow server-provided details
Submit an ENQUIRY to human providers (two steps; not a purchase)
Server description (copied; language not verified)
Submits an enquiry to M365 Migration Cost — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to relevant Microsoft 365 migration partners, who'll contact me directly."
Input schema (server-provided preview — do not copy)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answers",
"consent"
],
"properties": {
"answers": {
"type": "object",
"description": "the person's answers, keyed by field key",
"additionalProperties": {
"type": [
"string",
"number",
"boolean"
]
}
},
"consent": {
"type": "boolean",
"description": "true only when the person has agreed to: Happy for my details to go to relevant Microsoft 365 migration partners, who'll contact me directly."
},
"confirmation": {
"type": "string",
"description": "the confirmation token from step 1, after the person has approved the summary"
}
},
"additionalProperties": false
}
How to use this MCP
Talandor checks the server; it does not connect the server to your assistant.
Choose your client below, then copy the endpoint or configuration. Authentication is completed with the MCP provider, never inside Talandor.
This result does not yet expose a complete public contract or a qualified authentication surface, so there is nothing honest to watch yet. A Watch needs a complete public contract or a qualified authentication surface before it can monitor meaningful changes.
Full WatchAvailability, protocol, auth and public tool contract changes
Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff
Watch checkout is not open. This page does not start a payment. You can sign in from the header; that creates an account, not a Watch. Opening date: not announced yet. Hosted checkout remains closed.