[MrScraper (ai-mrscraper)]

This PR adds one new partner entry, partners/servers/mrscraper-mcp-server.json, for the hosted MrScraper MCP server. It is for the Microsoft Foundry tool catalog and the Azure API Center MCP registry. No other files change.

MrScraper will also submit the Azure API Center MCP Registry Sign-up form with a link to this PR.

What MrScraper MCP does

MrScraper is a web scraping service. The MCP server gives AI agents live web data through three read-only tools:

Tool	What it does
scraperAPI	Fetches a public URL and returns the page as HTML, Markdown, a screenshot, or a mix of these. Browser rendering runs automatically when needed and can be forced or turned off. Other options: geo-targeted proxies, wait-for-selector, custom request headers, timeout and retry limits.
webSearch	Runs a Google search from query text or a Google search URL, with region, language and page controls. It returns parsed organic results (title, link, description, rank) as JSON, or the raw result page as HTML.
status	Reports the connected account's subscription status, token usage, remaining tokens, rate limits and subscription end date.

All three tools are annotated readOnlyHint: true and destructiveHint: false. scraperAPI and webSearch are also openWorldHint: true. Each returns {status_code, data, headers, error?}, with credentials and cookies removed from the headers. Tool calls send the requested URLs, search queries and any options to MrScraper. Usage is counted against the account's MrScraper tokens.

Endpoint and authentication

Endpoint	https://mcp.mrscraper.com/mcp
Transport	Streamable HTTP (remoteType: streamable-http)
The entry declares two security schemes:

Scheme key	Type	Details
mrscraperBearerAuth	http, scheme: bearer	Authorization: Bearer <MrScraper API key>. Keys are created at https://app.mrscraper.com/api-tokens
mrscraperOAuth	oauth2, authorizationCode	OAuth 2.1 with PKCE (S256). Auth URL https://api.app.mrscraper.com/oauth/authorize, token and refresh URL https://api.app.mrscraper.com/oauth/token, scopes scrape:read (scraperAPI, webSearch), account:read (status) and offline_access

For Foundry, use the API key. MrScraper's OAuth clients come from dynamic client registration or client ID metadata documents. The sign-up form says Foundry does not support dynamic client registration yet, so key-based authentication (credential name Authorization, value Bearer <key>) is the method that works in Foundry today. The OAuth scheme is there for other MCP clients that support those registration methods. The endpoints come from the authorization server metadata at https://api.app.mrscraper.com/.well-known/oauth-authorization-server. The protected-resource metadata is at https://mcp.mrscraper.com/.well-known/oauth-protected-resource/mcp. No authSchemas value is set, because MrScraper has no managed OAuth client for Foundry yet. If you would like managed OAuth for Foundry, please let us know and we will look at registering a client for it.

The entry

Field	Value
name	mrscraper-mcp
title	MrScraper MCP
kind / vendor	mcp / Partner
remote / remoteType	https://mcp.mrscraper.com/mcp / streamable-http
categories	Web
license	MIT, https://github.com/mrscraper-com/mrscraper-mcp/blob/main/LICENSE
repository	https://github.com/mrscraper-com/mrscraper-mcp (source of the server, MIT)
externalDocumentation	https://docs.mrscraper.com/docs/getting-started/mcp-server
icon	512×512 PNG with a transparent background, so it works in light and dark themes
supportContactInfo	MrScraper Support, support@mrscraper.com
useCases	Web page scraping, page screenshots, Google web search, account usage
securitySchemes	mrscraperBearerAuth (bearer API key), mrscraperOAuth (OAuth 2.1 with PKCE)
versionName / x-ms-preview	original / false (generally available)

The layout follows the existing remote web-data entries (brightdata-mcp-server.json, browserbase-mcp.json, parallel-search-mcp-server.json, exa-mcp-server.json). Declaring a bearer scheme and an oauth2 scheme side by side follows github-mcp-server.json, neon-mcp-server.json and supabase-mcp-server.json. summary is one line of 134 characters, description is 963 characters and the OAuth scheme description is 184 characters.

Validation

I ran the three steps of .github/workflows/validate-servers.yml locally with Python 3.12 and check-jsonschema 0.38.2:

$ check-jsonschema --verbose --schemafile partners/server-schema.json partners/servers/*.json
ok -- validation done

Validate server names are unique:
All 115 server names are unique across JSON files

Validate security schema keys are unique:
All 124 security scheme keys are unique across JSON files

Endpoint and link checks (no real credentials used):

• GET https://mcp.mrscraper.com/mcp with no credentials returns 401, with WWW-Authenticate: Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.mrscraper.com/.well-known/oauth-protected-resource/mcp".
• An MCP initialize POST with a made-up bearer value returns 401 with "error_description":"Invalid MrScraper API token", so the server checks bearer values as MrScraper API keys.
• The protected-resource metadata and https://api.app.mrscraper.com/.well-known/oauth-authorization-server both return 200 with JSON. The authorization server metadata lists the authorize and token URLs used in mrscraperOAuth, PKCE S256, and the scopes scrape:read, scrape:write, account:read and offline_access.
• The icon, license, repository, documentation and API-token page URLs all return 200.

Not covered here: authenticated tool calls, an OAuth sign-in, and an end-to-end connection from Foundry Agent Service. These need a MrScraper API key or account, which this submission environment does not have. The Foundry check (at least five queries through a custom MCP tool, as the sign-up form asks) will be done by the MrScraper team with an Azure subscription and reported in the form.

Contact

MrScraper Support, support@mrscraper.com. Docs: https://docs.mrscraper.com. We're happy to change anything the review calls for.

This PR comes from MrScraper, which runs this service.

🤖 Generated with Claude Code

[microsoft-github-policy-service]

MrScraper (@ai-mrscraper) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

[MrScraper (ai-mrscraper)]

Linda Li (@lindazqli) Yongjia Li (@yongjiaaaa) could you take a look when you have a moment? This adds the MrScraper MCP partner entry (partners/servers/mrscraper-mcp-server.json). All three checks in validate-servers.yml passed locally. MrScraper will also submit the Azure API Center MCP Registry Sign-up form with a link to this PR. Thank you!