WyndPath Web Data
com.wyndpathPublished by wyndpath.comOfficial publisherv1.0.0Updated Oct 24, 2026
Fetch and extract data from any public web page, even JS-rendered or anti-bot protected
Overview
Lets an assistant fetch and extract data from public web pages, including JavaScript-rendered or anti-bot protected ones.
- What you can do
- WyndPath Web Data is a remote MCP server that retrieves content from public web pages and extracts data from them. According to its registry description, it handles pages that are JavaScript-rendered or protected by anti-bot measures, which ordinary simple fetches often cannot read. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant needs page content that plain HTTP fetching fails to return, such as single-page apps, dynamically loaded pages, or sites that block simple requests. It is less useful for static pages that a basic fetch already handles.
- Requirements
- A remote endpoint at mcp.wyndpath.com over streamable HTTP; nothing runs locally. Authentication is required: either OAuth sign-in, which opens wyndpath.com in the client, or an Authorization header carrying a WyndPath API key in the form 'Bearer '. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open WyndPath Web Data in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.wyndpath%2Fweb-data-extraction/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"wyndpath-web-data": {
"type": "http",
"url": "https://mcp.wyndpath.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.