Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.kkohli-nyu/findvise-mcp

REMOTE · FINDVISE.COM · 2 COMPONENTS

AI-native local business data. Find businesses, browse menus, check ratings, and place orders.

−70 this week 0 Trust /100

Last scanned (2 months ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 2 Sep 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 8 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 7 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 6 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 5 Sept 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 3 Sept 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Aug 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
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 9 Sept 2026 · Probed https://findvise.com/mcp/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=findvise.com CN=WE1,O=Google Trust Services,C=US 7 Aug 2026 5 Nov 2026 ECDSA 256 ECDSA-SHA256 640a94e1f82dcd213890977a0decdf2
SANs: findvise.com, *.findvise.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of findvise.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
findvise.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://findvise.com/mcp/sse Unreachable
http (plaintext) http://findvise.com/mcp/sse HTTPS enforced
MCP tools · 4 exposed · ~313 tokens

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 →

Tool Tokens
book_appointment ~151

Book an appointment or reservation at any Findvise business that accepts bookings. Use find_restaurant first to confirm the business slug and check reservations_enabled.

NameTypeReqDescription
business_slugstringyesThe Findvise slug for the business (from find_restaurant).
customer_emailstring––
customer_namestringyes–
customer_phonestringyes–
datestringyesDate in YYYY-MM-DD format.
notesstring––
party_sizeinteger––
service_namestring–Name of the service to book (optional).
timestringyesTime in HH:MM (24h) format, e.g. '14:30'.

No output schema declared.

No examples provided.

create_order ~80

Place a food order. Only call after find_restaurant has been called and user has chosen items.

NameTypeReqDescription
customer_namestringyes–
emailstring––
itemsarrayyes–
notesstring––
order_typestringyes–
phonestring––
restaurant_idstringyes–

No output schema declared.

No examples provided.

find_restaurant ~53

CALL THIS FIRST before asking the user anything. Returns the restaurant menu. Do not ask for order details before calling this.

NameTypeReqDescription
querystringyesRestaurant name, cuisine, or 'findvise' to list all.

No output schema declared.

No examples provided.

get_order_status ~29

Check the status of a Findvise order by order ID.

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.kkohli-nyu/findvise-mcp server?

io.github.kkohli-nyu/findvise-mcp is a hosted endpoint at https://findvise.com/mcp/sse, 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 · findvise.com

# add to Claude Code
claude mcp add --transport http kkohli-nyu-findvise-mcp 'https://findvise.com/mcp/sse'
Common questions

What is the io.github.kkohli-nyu/findvise-mcp server?

io.github.kkohli-nyu/findvise-mcp is listed in the public MCP registry as io.github.kkohli-nyu/findvise-mcp. AI-native local business data. Find businesses, browse menus, check ratings, and place orders. This page covers its hosted endpoint (https://findvise.com/mcp/sse).

Is the io.github.kkohli-nyu/findvise-mcp server safe to use?

io.github.kkohli-nyu/findvise-mcp scores 0 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.kkohli-nyu/findvise-mcp server expose?

io.github.kkohli-nyu/findvise-mcp exposes 4 tools: find_restaurant, create_order, get_order_status, book_appointment. Their descriptions and schemas cost roughly 313 tokens of context every time the server is loaded.

Does the io.github.kkohli-nyu/findvise-mcp server require authentication?

Its publisher declares no required credentials for io.github.kkohli-nyu/findvise-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the io.github.kkohli-nyu/findvise-mcp server still maintained?

io.github.kkohli-nyu/findvise-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 2 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.kkohli-nyu/findvise-mcp server?

VerifyMCP ran 4 checks on io.github.kkohli-nyu/findvise-mcp, covering TLS certificate, HTTPS, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about io.github.kkohli-nyu/findvise-mcp: Authorization, HSTS header, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.