Skip to content

Overlap MCP server

com.overlap-ai/overlapoverlap-ai.comstreamable-httpv0.3.0Scanned

Records what you're working on so Overlap can introduce you to someone two weeks ahead of you.

7 tools: 3 can delete or cancel things, 2 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 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 Overlap MCP server can do

The Overlap MCP server is published by overlap-ai.com, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (3 tools: create_match_request, respond_to_match and withdraw_match_request) and create or change data (2 tools: confirm_match_request and check_matches). 2 tools only read.

2 tools bring in text other people can write (confirm_match_request and respond_to_match).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 0.3.0.

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.

7 tools

Deletes or cancels 3Claude Code: deny
  • create_match_requestUse this tool to save a private match request draft when the user wants to find a peer living through a similar personal situation.No findings

    Why it is in this group

    • The name "create_match_request" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Use this tool to save a private match request draft when the user wants to find a peer living through a similar personal situation. Write the match request from the current conversation. Write 2–5 sentences in the third person, and 200–1500 characters. Use the words of the user, not formal or clinical words. Cover three things: the situation, where the user is in it, and what help they want. Write it so that a stranger in the same place recognizes themselves. Any situation belongs here: an illness, a company, a move, a course, a hard year. Example of a good match request: "She was diagnosed with early-stage breast cancer four months ago and is halfway through chemotherapy. The medical side goes to plan. She finds the isolation harder than the treatment. The people around her keep telling her to stay positive. She hopes to hear from someone at a similar stage who understands the day-to-day of it." Never invent a detail. Never include a name, an email address, an employer or another personal identifier. With no replaces_draft_id, this tool saves a new independent private draft. With replaces_draft_id, it saves the complete revised text as a new draft and supersedes only the identified earlier draft. Existing open requests remain unchanged. The draft is not submitted to the matching pool and contacts nobody. Returns request_id, status and the exact stored request_text. Publishing uses the separate confirm_match_request tool and requires the user’s explicit approval of that exact stored text. Discarding uses withdraw_match_request with the draft’s request_id.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • respond_to_matchRecord the one answer the user gave about a match: accept, decline or block.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • 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
    Record the one answer the user gave about a match: accept, decline or block. Call it only after the user has said which of the three they want. When both people accept, overlap opens a private conversation in the app. It also sends each person a link by email. Never promise an address. A decline covers this one request, and a later request from that person can still match. A block is permanent and covers the person, so send block only when the user asks for exactly that.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • withdraw_match_requestWithdraw one match request, either a draft or an open one.No findings

    Why it is in this group

    • The name "withdraw_match_request" says "withdraw": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Withdraw one match request, either a draft or an open one. Always pass its request_id. If it is unclear which one the user means, call check_matches first. The other requests of the user stay active. This voids a pending match from this request. It keeps a match that both people accepted.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 2Claude Code: ask
  • check_matchesWhere the user stands.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Where the user stands. It returns every current match request, the number of other people in the pool, and any match. Use it to answer what the user submitted, and who they matched with. A match can appear days later.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • confirm_match_requestConfirm one draft match request and add it to the matching pool.Reads text others writeNo findings

    Why it is in this group

    • The name "confirm_match_request" says "request": a word for a change.

    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
    Confirm one draft match request and add it to the matching pool. The other requests of the user do not change. It stays active until the user withdraws it. Call this ONLY after the user approves the exact stored text. Always pass its request_id.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_match_detailsGet the full details of one match: what the other person wrote, why the two of them matched, something to open with, and where the match stands.No findings

    Why it is in this group

    • The name "get_match_details" says "get": a word for reading.
    Description, as the server wrote it
    Get the full details of one match: what the other person wrote, why the two of them matched, something to open with, and where the match stands. It only reads. To accept, decline or block the match, call respond_to_match. Never promise an address.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_poolCount people in overlap's peer-connection pool who are going through a similar personal situation.No findings

    Why it is in this group

    • The name "preview_pool" says "preview": a word for reading.
    Description, as the server wrote it
    Count people in overlap's peer-connection pool who are going through a similar personal situation. Use when the user asks whether another person shares their situation before deciding whether to join. Do not use for intersections of lists, sets or schedules, dating, or finding licensed professionals. Returns a number and nothing else, capped at 10 — never anyone's words, name or details. It saves nothing: no match request is created and nobody is contacted. This is the one tool that works without an account.

    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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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:44 UTC, unchanged since Oct 22, 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
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://overlap-ai.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://kawaynstkgszajxniuao.supabase.co/auth/v1
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 5 tools that change things (3 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://overlap-ai.com/api/mcp: tools/list returned 7 tools to an anonymous client, including create_match_request (destructive), respond_to_match (destructive), withdraw_match_request (destructive), confirm_match_request (write), check_matches (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http overlap https://overlap-ai.com/api/mcp
claude mcp add --transport http overlap https://overlap-ai.com/api/mcp

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__overlap__preview_pool",
      "mcp__overlap__get_match_details"
    ],
    "ask": [
      "mcp__overlap__confirm_match_request",
      "mcp__overlap__check_matches"
    ],
    "deny": [
      "mcp__overlap__create_match_request",
      "mcp__overlap__respond_to_match",
      "mcp__overlap__withdraw_match_request"
    ]
  }
}

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 overlap. Review it before you use it.

Capability tags behind 2 rules
  • mcp__overlap__confirm_match_request untrusted-input
  • mcp__overlap__respond_to_match 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.overlap-ai/overlap/verify?hash=a5682ffafd8647a78896f6d6b7841b74250e285c66516c2cb7f5eae1adef8c4b" | jq -e '.changed == false'

Pinned hash a5682ffafd86, from Nov 14, 2026, 00:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.overlap-ai/overlap/changes.xml

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

Badge

Anlyon Radar badge for com.overlap-ai/overlap
[![Anlyon Radar](https://radar.anlyon.com/badge/com.overlap-ai/overlap.svg)](https://radar.anlyon.com/servers/com.overlap-ai/overlap)

Source: MCP Registry. Synced Oct 21, 2026, 18:00 UTC.

Overlap MCP server: questions and answers

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

Is the Overlap MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 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 Overlap MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: create_match_request, respond_to_match and withdraw_match_request.

Can the Overlap 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 Overlap MCP server have?

7 tools: 3 destructive, 2 write, 2 read. create_match_request, respond_to_match, withdraw_match_request, confirm_match_request, check_matches, preview_pool and get_match_details.

Does the Overlap MCP server need sign-in or OAuth?

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

Does the Overlap MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Overlap MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.