Search MCP servers from your browser's address bar

VerifyMCP publishes an OpenSearch description, so you can add it to your browser as a search engine and query the directory straight from the address bar. Type a shortcut, type a server name, and go directly to its trust score without loading the site first.

Every modern browser can do this. None of them will offer it to you, which is why this page exists.

What you get

Once the engine is added, typing your chosen shortcut in the address bar puts the browser into VerifyMCP search mode. From there:

• Live completions as you type. The browser calls /opensearch/suggest.json, which ranks results exactly like the on-page search does: an exact name match beats a prefix, which beats a suffix, which beats a substring.
• Only scored servers are suggested. The homepage hides unscored servers by default, so suggesting one would send you to an empty results page.
• Trust scores travel with the suggestion. Each completion carries its score out of 100 as a description. Whether you see that depends on the browser (see what the integration serves).
• Pressing Enter runs a normal search. You land on the directory at /?q=<your term>, the same page the on-page search box produces.

Suggestions are matched against an in-memory snapshot of the directory, so the lookup itself does no database work and keeps up with typing.

Add it in Chrome

Chrome will have registered VerifyMCP quietly the first time you visited the site. It does not prompt, and it does not activate the engine for you.

1. Visit verifymcp.io at least once.
2. Open chrome://settings/searchEngines.
3. Find Site search, then look under Inactive shortcuts for VerifyMCP.
4. Select Activate, and set the shortcut you want to type (mcp works well).

If it is not listed, add it by hand in the same panel. Select Add next to Site search and fill in:

A hand-added engine does not get live suggestions. Chrome only wires those up for an engine it discovered itself, so prefer activating the discovered entry where you can.

Add it in Edge

Edge is the strictest of the three. It never adds an engine silently and never prompts, and it only fetches the description document at the moment you choose to add the engine. Three conditions must hold first:

• You have visited the site at its path-less root, https://verifymcp.io/ (at most one redirect). Arriving on a deep page does not count.
• The description link is in the main frame, not an iframe.
• Both the page and the description file are served over HTTPS.

VerifyMCP satisfies all three, so:

1. Visit verifymcp.io.
2. Open edge://settings/searchEngines (Settings, then Privacy, search and services, then Address bar and search, then Manage search engines).
3. Find VerifyMCP in the list and give it a shortcut, or select Add and use the same three values as the Chrome table above.

Add it in Firefox

Firefox removed the address-bar affordance that used to offer search engines, so there is nothing to click on the page itself. Add it through settings:

1. Open about:preferences#search.
2. Scroll to Search Shortcuts and select Add at the bottom.
3. Fill in the name, the URL, and an optional keyword, then select Add Engine.

Safari and other browsers

Safari does not support this. It offers a fixed list of search providers and does not read OpenSearch descriptions from arbitrary sites, so VerifyMCP cannot be added as a Safari search engine. Bookmarking https://verifymcp.io/?q= is the closest equivalent.

Chromium-derived browsers (Brave, Vivaldi, Arc, Opera) behave like Chrome, and their settings pages sit at the same ://settings/searchEngines path.

Why your browser never offered it

If you expected a prompt, you are remembering how browsers used to behave. The prompt is gone everywhere, and each browser removed it differently:

• Chrome registers a discovered engine as inactive and files it under Site search. It is present in settings from the first visit, but it does nothing until you activate it by hand.
• Edge does not even fetch the description document until you explicitly choose to add the engine, and it gates discovery on that path-less root visit.
• Firefox dropped the address-bar “add search engine” control. It surfaces the option only on the optional separate search bar, so a default Firefox profile gives no indication at all.

MDN states the position plainly: autodiscovery behaviour “varies among browsers” and is not guaranteed to be surfaced to the user. A site can publish a perfectly valid description and still look, from the outside, as though nothing is implemented.

What the integration actually serves

Two endpoints back this, and both are public if you want to build against them.

The suggestions endpoint takes a single q parameter and returns the standard OpenSearch Suggestions array of four elements:

[
  "git",
  ["io.github.Dave-London/git", "Git"],
  ["Trust score 94/100", "Trust score 49/100"],
  ["https://verifymcp.io/servers/dave-london-git", "https://verifymcp.io/servers/abhishekkumar2021-git"]
]

Element 0 is the query echoed back, element 1 the completions, element 2 the trust scores, element 3 the canonical server URLs. Browsers read the first two. Firefox ignores the trailing arrays and Chrome will not navigate a third-party engine to them, so treat them as a description of the match rather than as a click target: selecting a suggestion always goes through the search URL.

Queries shorter than two characters return an empty result set. A single character matches most of the catalogue, so the ten rows it would return are close to arbitrary.

Result URLs point at /servers/<slug>, which redirects to whichever channel of that server currently scores best, so a suggestion always lands on the headline result.

Troubleshooting

Next

• Browse the directory that these searches query
• Read how the trust scores in the suggestions are calculated
• See the remote endpoint rubric and the package rubric