Skip to content

Odile Labs MCP server

com.odilelabs/odileodilelabs.comstreamable-httpv1.9.2Scanned

Odile Labs: AI agents reach businesses by phone number (Direct); Gate keys, audit. Agentforce-ready.

14 tools: 5 can delete or cancel things, 4 change things and 5 only read.

Tools: 5 delete, 0 irreversible, 4 write, 5 read.
  • Reads private data · 2
  • Reads text others write · 8
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Odile Labs MCP server can do

The Odile Labs MCP server is published by odilelabs.com, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (5 tools: send_to_business, cancel_request, reply_to_business, call_business and 1 more) and create or change data (4 tools: open_request, get_request, claim_request and get_direct_payment). 5 tools only read.

2 tools read private data (find_business_agent and get_replies); 8 tools bring in text other people can write (send_to_business, get_request, cancel_request and 5 more); 2 tools can send data out of your system (send_to_business and reply_to_business). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.9.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 5Claude Code: deny
  • answer_call_questionGive the calling assistant your answer to a question the business asked during a call placed with call_business, so the call can continue.Reads text others writeNo findings

    Why it is in this group

    • The name "answer_call_question" says "call": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Give the calling assistant your answer to a question the business asked during a call placed with call_business, so the call can continue. Use it only when get_call_result shows state input_required (its pending_question holds the question); reply within 45 seconds or the assistant tells the business the person will follow up and carries on. The assistant uses the answer on the live call and it cannot be taken back, so keep it short and factual (up to 300 characters). It is refused if it contains a number of four to eight digits, a card-length number, or words such as password, PIN or code; never include payment card numbers, passwords or one-time codes. Requires direct:tasks and ownership of the call. Returns the call state; read get_call_result for the outcome. Example: task_id='dv_9a3', answer='A 40-gallon gas heater, installed in 2016.'

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • call_businessPlace an outbound phone call to a business to ask for information on a named person’s behalf.Reads text others writeNo findings

    Why it is in this group

    • The name "call_business" says "call": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Place an outbound phone call to a business to ask for information on a named person’s behalf. Use it when find_business_agent returned not_found for a US or Canadian number; when a Direct card exists use send_to_business. It dials a real number and a call cannot be recalled once placed. Requires direct:tasks, human opt-in at https://odilelabs.com/developers#voice and the person’s permission for this call (on_behalf_consent true). Informational calls only: no sales, payments or account access. Calls run Monday to Friday, 9:00 to 17:00 in the business’s local time; outside that window the request is refused and the error includes next_window. A number is not called twice within 24 hours, and each account has a daily call cap. number and callback_number must be callable US or Canadian E.164 numbers, callback_number being the person’s own, never the business’s. message_id is required: reuse it unchanged on every retry so only one call is placed. Returns {task_id, state (queued, completed or failed), status}; read get_call_result for progress and answers. Voice credit costs: get_m2m_network. Example: number='+15615550123', business_name='Harbor Plumbing', caller_name='Ana Diaz', callback_number='+15615550199', need='Do you replace water heaters?', on_behalf_consent=true, message_id='call-8f2'.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • cancel_requestCancel the confirmed booking attached to a request you can access.Reads text others writeNo findings

    Why it is in this group

    • The name "cancel_request" says "cancel": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Cancel the confirmed booking attached to a request you can access. This does not close the request or revoke assistant grants. It cannot be undone; only do it when the customer asked. Use this for a booking made under a request; for one made without a request, use send_to_business with the cancel_booking skill. Needs a live grant with scope read_cancel or book. Calling it again returns the same result. Returns cancelled, booking_id and when. Refused with outcome_uncertain when the calendar cannot confirm the booking (read get_request), and grant_required without access. Requires direct:tasks.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • reply_to_businessAnswer a business in an existing Direct conversation.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "reply_to_business" says "reply": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "reply_to_business" says "reply": it sends or publishes something to other people.
    Description, as the server wrote it
    Answer a business in an existing Direct conversation. Use it after get_replies shows the business answered or asked something; to start a new conversation use send_to_business, and to answer a question during a live phone call use answer_call_question. Pass the thread_id that send_to_business returned and the reply text (1 to 500 characters); sign in as the original requester with direct:tasks, or supply the private thread_token instead. message_id is the retry key: reuse it unchanged when retrying. Returns the A2A {task} for the reply: read its state before telling anyone it was delivered. A delivered reply cannot be recalled and is billed the same way as a take_message task; closed conversations refuse replies. Example: thread_id='th_7c1', text='Thursday after 2pm works, thank you.', message_id='rep-1'.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • send_to_businessStart contact with a business on Direct for a message, availability check or booking.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_to_business" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_to_business" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Start contact with a business on Direct for a message, availability check or booking. Call find_business_agent first; for a business without a card, use call_business. Say an automated assistant is acting, and get the person's permission before booking. A delivered message cannot be recalled. Use the cancel_booking skill only for a booking made through send_to_business, with its booking_id and cancel_token. message_id is the retry key: reuse it unchanged on every retry so the request runs once. If you omit it, an identical request from you counts as a retry only within the same UTC day. Returns the A2A v1.0 {task}: read its state before telling anyone a message was delivered or a booking confirmed. A deposit booking returns INPUT_REQUIRED with a payment_url for the person; it is held 30 minutes and confirmed only after payment, which get_direct_payment checks. Failed, refused and unconfirmed tasks are not charged; costs are in get_m2m_network and your balance in get_direct_usage. Messages and confirmed bookings return thread_id and thread_token: use get_replies to read the business’s replies and reply_to_business to answer in the same conversation. Signed-in requesters may omit callback_number for take_message; anonymous requesters still need their own valid number. Example: biz='harbor-plumbing', skill='take_message', message_id='req-8f2', data={caller_name:'Ana Diaz', callback_number:'+15615550199', need:'Leaking water heater, today if possible'}.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 4Claude Code: ask
  • claim_requestTake over a request another assistant opened, using the single-use handoff code the customer issued from their customer link.No findings

    Why it is in this group

    • The name "claim_request" says "request": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Take over a request another assistant opened, using the single-use handoff code the customer issued from their customer link. Use it only when the customer gave you a code; to start a new job use open_request. The code is used up by a successful claim and expires after 15 minutes. Your access is the scope the customer chose: read, read_cancel or book. Returns request_id and your grant; a bad, used or expired code is refused. Call get_request next. Requires direct:tasks.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • get_direct_paymentCheck an existing deposit booking on your signed-in Direct account: reconcile its Stripe Checkout payment and return its receipt and the separate booking state.Reads text others write1 finding

    Why it is in this group

    • The name "get_direct_payment" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "get_direct_payment" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_direct_payment" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Check an existing deposit booking on your signed-in Direct account: reconcile its Stripe Checkout payment and return its receipt and the separate booking state. Use it after send_to_business returned a payment_url for a deposit booking, to see whether the person has paid; it cannot start a payment, which the person makes on Stripe’s hosted page. Pass biz (the business id from its card) and task_id (the task id send_to_business returned for that booking). Requires direct:tasks. Uses only the stored merchant account and amount and creates no new charge or booking identity; a verified paid checkout may finish its already-authorized held booking. Payout status remains unknown: paid does not mean a bank payout. Safe to repeat. Example: biz='harbor-plumbing', task_id='tk_5d0' after send_to_business returned a payment_url for a deposit booking.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_requestRead a request you hold a grant on: objective, attempts, facts, booking, your_scope and next_allowed.Reads text others write1 finding

    Why it is in this group

    • The name "get_request" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "get_request" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_request" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read a request you hold a grant on: objective, attempts, facts, booking, your_scope and next_allowed. It checks any booking against the business calendar and updates the stored record and billing to match, but never books, moves or cancels anything and contacts nobody; repeat it freely. Use it after a booking, and after claim_request, before acting. Not for a conversation started without a request (get_replies). next_allowed is book, cancel, read or needs_human; a fact marked uncertain means the calendar could not confirm it. Refused with grant_required or grant_revoked when you have no live grant. Requires direct:tasks.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • open_requestCreate a customer-controlled booking request that another assistant can continue.No findings

    Why it is in this group

    • The name "open_request" says "open": a word for a change.
    Description, as the server wrote it
    Create a customer-controlled booking request that another assistant can continue. Use it first when another assistant may need to continue the job; for a one-off message or booking, use send_to_business alone. It contacts nobody and books nothing. Returns request_id, customer_link and your grant (scope book). Show the customer link (customer_link) to the person before acting: it is how they see the request, revoke an assistant and issue a handoff code. Treat it as private. Then book with send_to_business, passing request_id. Requires direct:tasks.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • find_business_agentLook up a business by its phone number in the Odile Direct directory and get its Direct card.Reads private dataNo findings

    Why it is in this group

    • The name "find_business_agent" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "directory": it reads files.
    Description, as the server wrote it
    Look up a business by its phone number in the Odile Direct directory and get its Direct card. Start here: send_to_business needs the business id (<biz>) from this card. Pass the number as customers dial it, in E.164 with the country code and no spaces or dashes (+15615550123); any other format is rejected. Returns {agent_card, business, trade, town}: agent_card is the A2A card URL (/b/<biz>/ for a business line, /c/<biz>/ for a claimed listing; pass that <biz> to send_to_business), and the card lists the skills the business accepts. A number that is not on Direct returns not_found with claim_url and listings_url; for a US or Canadian number, voice_fallback says whether call_business is available. Capped at 30 lookups per IP per hour without sign-in and 10000 per key per day signed in. Read-only; contacts no business. Example: number='+15615550123' returns the card whose id you pass to send_to_business as biz.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_call_resultRead the state and outcome of a business call you placed with call_business (an outbound call), using its task_id.No findings

    Why it is in this group

    • The name "get_call_result" says "get": a word for reading.
    Description, as the server wrote it
    Read the state and outcome of a business call you placed with call_business (an outbound call), using its task_id. Call it again until the state is final: queued, dialing and in_call are still in progress; completed, no_answer, voicemail, refused and failed are final; input_required means the business asked a question that answer_call_question can answer within 45 seconds. Requires direct:tasks and ownership of the call (another account’s task_id returns Not found). Returns {task_id, state, outcome, duration_seconds, transcript, answers, summary, cost {credits}}, plus pending_question {question, expires_at} while a question waits. Changes nothing, starts no call and is safe to repeat. Example: task_id='dv_9a3' from call_business; stop polling once state is completed, failed or no_answer.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_direct_usageRead your own Direct account ledger: the signed-in account’s UTC free-send allowance, prepaid balance in cents, reserved cents and last 20 charges.No findings

    Why it is in this group

    • The name "get_direct_usage" says "get": a word for reading.
    Description, as the server wrote it
    Read your own Direct account ledger: the signed-in account’s UTC free-send allowance, prepaid balance in cents, reserved cents and last 20 charges. It never buys credit and does not list costs (see get_m2m_network). Use it before sending tasks that may cost credit; a payment_required reply from send_to_business carries the top-up link. Uses the same ledger as REST and your developer page. Requires direct:tasks and sign-in. Changes nothing; phone minutes and legacy credits are tracked separately. Example: call it with no arguments before a booking to confirm the allowance or balance covers it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_m2m_networkRead the OdileM2M network card for Direct: the live skills a business can accept, what each costs in credits, the credit packs, the limits that apply, and the Gate MCP address and …No findings

    Why it is in this group

    • The name "get_m2m_network" says "get": a word for reading.
    Description, as the server wrote it
    Read the OdileM2M network card for Direct: the live skills a business can accept, what each costs in credits, the credit packs, the limits that apply, and the Gate MCP address and quickstart. Use it to cost Direct tasks before sending any. For your own balance use get_direct_usage. Returns the pricing card (currency, credit_cents, packs, lookups) plus live_skills[{id, name, description, credits}], receipts, mcp_url, gate_mcp_url, quickstart_url, docs_url and connect_steps[]. Reference data, nothing account-specific: takes no arguments, needs no sign-in, contacts no business and changes nothing. Example: call it once with no arguments before the first send_to_business of a session.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_repliesRead the replies in a Direct conversation you started with send_to_business: its status and messages, newest last.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_replies" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "conversation": it reads messages.
    • untrusted-inputThe name "get_replies" says "get" and "reply": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    Read the replies in a Direct conversation you started with send_to_business: its status and messages, newest last. Use it to find out whether the business has answered; it only reads and does not wait, so call it again later if there is no reply yet. For the outcome of a phone call use get_call_result. Pass the thread_id that send_to_business returned; sign in as the original requester with direct:tasks, or supply the private thread_token instead. Returns {thread_id, status (received, business_notified, business_replied, booked, waiting_for_you or closed), caller_name, callback_number, messages[{from: customer or business, text, at}]}. An unknown thread or a wrong token returns not_found, and a thread expires 90 days after its last message. Changes nothing and uses no credits. Example: thread_id='th_7c1' (with thread_token unless you started the thread while signed in) returns the status and messages so far.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

32 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__odile__reply_to_business",
      "mcp__odile__send_to_business"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://odilelabs.com/.well-known/oauth-protected-resource/mcp/direct
Authorization servers
https://odilelabs.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (5 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://odilelabs.com/mcp/direct: tools/list returned 14 tools to an anonymous client, including send_to_business (destructive), cancel_request (destructive), reply_to_business (destructive), call_business (destructive), answer_call_question (destructive) and 4 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 6 to 9
    • RFC 9728 protected resource metadata: https://odilelabs.com/.well-known/oauth-protected-resource/mcp to https://odilelabs.com/.well-known/oauth-protected-resource/mcp/direct
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 11 to 6

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "get_request" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_request" says "get": a word for reading.

    What this check looks for
  • The server marks "get_direct_payment" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "get_direct_payment" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff
  2. Tools4 added, 10 changed.+4 added~10 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 9; RFC 9728 protected resource metadata: https://odilelabs.com/.well-known/oauth-protected-resource/mcp -> https://odilelabs.com/.well-known/oauth-protected-…View diff
    • Tools that change things, listed without credentials: 6 to 9
    • RFC 9728 protected resource metadata: https://odilelabs.com/.well-known/oauth-protected-resource/mcp to https://odilelabs.com/.well-known/oauth-protected-resource/mcp/direct
  4. Tools5 added, 10 removed, 5 changed.+5 added−10 removed~5 changedView diff
  5. Tools9 changed.~9 changedView diff
    • Changed:buy_packChanges thingsdescriptioninputSchema
    • Changed:find_business_agentOnly readsdescriptioninputSchema
    • Changed:get_agent_servicesOnly readsdescription
    • Changed:get_answering_lineOnly readsdescription
    • Changed:get_direct_paymentChanges thingsinputSchema
    • Changed:get_direct_usageOnly readsdescription
    • Changed:get_m2m_networkOnly readsdescription
    • Changed:get_sip_addressChanges thingsdescription
    • Changed:send_to_businessDeletes or cancelsdescriptioninputSchema
  6. Tools9 removed, 8 changed.−9 removed~8 changedView diff
    • Removed:create_media_job
    • Removed:estimate_meal_photo
    • Removed:estimate_media_job
    • Removed:get_balance
    • Removed:get_catalog
    • Removed:get_downloads
    • Removed:get_job
    • Removed:prepare_upload
    • Removed:unlock_job
    • Changed:buy_packChanges thingstitledescriptioninputSchema
    • Changed:get_answering_lineOnly readsdescription
    • Changed:get_answering_line_offerOnly readstitledescription
    • Changed:get_direct_usageOnly readsdescription
    • Changed:get_receptionist_benchmarkOnly readsdescription
    • Changed:get_sip_addressChanges thingsdescription
    • Changed:send_to_businessDeletes or cancelsdescriptioninputSchemaannotations
    • Changed:set_up_answering_lineChanges thingstitledescriptioninputSchema
  7. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 6.View diff
    • Tools that change things, listed without credentials: 11 to 6
  8. Tools4 added, 2 changed.+4 added~2 changedView diff

Install

Pinned to version 1.9.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http odile https://odilelabs.com/mcp/direct
claude mcp add --transport http odile https://odilelabs.com/mcp/direct

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__odile__get_m2m_network",
      "mcp__odile__find_business_agent",
      "mcp__odile__get_replies",
      "mcp__odile__get_call_result",
      "mcp__odile__get_direct_usage"
    ],
    "ask": [
      "mcp__odile__open_request",
      "mcp__odile__get_request",
      "mcp__odile__claim_request",
      "mcp__odile__get_direct_payment"
    ],
    "deny": [
      "mcp__odile__send_to_business",
      "mcp__odile__cancel_request",
      "mcp__odile__reply_to_business",
      "mcp__odile__call_business",
      "mcp__odile__answer_call_question"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as odile. Review it before you use it.

Capability tags behind 9 rules
  • mcp__odile__find_business_agent private-data
  • mcp__odile__send_to_business untrusted-input, outbound
  • mcp__odile__get_request untrusted-input
  • mcp__odile__cancel_request untrusted-input
  • mcp__odile__get_replies private-data, untrusted-input
  • mcp__odile__reply_to_business untrusted-input, outbound
  • mcp__odile__call_business untrusted-input
  • mcp__odile__answer_call_question untrusted-input
  • mcp__odile__get_direct_payment untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.odilelabs/odile/verify?hash=711ca627dbd23a2fc29577518ce1b80b29b0fe98350452727fd3bc2c5ad7693d" | jq -e '.changed == false'

Pinned hash 711ca627dbd2, from Nov 14, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.odilelabs/odile/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.odilelabs/odile
[![Anlyon Radar](https://radar.anlyon.com/badge/com.odilelabs/odile.svg)](https://radar.anlyon.com/servers/com.odilelabs/odile)

Source: MCP Registry. Synced Nov 14, 2026, 22:17 UTC.

Odile Labs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Odile Labs MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 9 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Odile Labs MCP server delete data?

Yes. 5 tools can delete, cancel or revoke something: send_to_business, cancel_request, reply_to_business, call_business and answer_call_question.

Can the Odile Labs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Odile Labs MCP server have?

14 tools: 5 destructive, 4 write, 5 read. send_to_business, cancel_request, reply_to_business, call_business, answer_call_question, open_request, get_request, claim_request and 6 more.

Does the Odile Labs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Odile Labs MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_to_business and reply_to_business.

Has the Odile Labs MCP server changed its tools?

Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.