Smithery Ai Fetch

ai.smitheryPublished by smithery.aiOfficial publisherv1.0.0Updated Oct 24, 2026

A simple tool that performs a fetch request to a webpage.

The publisher's own server: 222wcnm Bilistalkermcp

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant fetch a webpage over HTTP and return its content for reading or extraction.

What you can do
This remote MCP server exposes a single fetch capability: it performs an HTTP request to a given webpage and returns the response content to the assistant. It is a thin retrieval utility rather than a full browsing or scraping suite, so it is useful for pulling a page's contents into a conversation.
When to use it
Add it when the assistant needs to retrieve a specific web page by URL and work with its content, for example to read an article or check a page's current text. It is not a substitute for search, crawling, or interactive browser control.
Requirements
A remote MCP endpoint at reachable over the network. Authentication is required: an Authorization header carrying a bearer token for Smithery. No local runtime or package is declared.
Before you install
The Authorization header carries a bearer token, so treat it as a secret and avoid exposing it in logs or shared configuration. Fetched pages are requested from third-party sites, which will see the request; content returned from the web should be treated as untrusted input.

Installation

In SourceWeft

  1. Open Smithery Ai Fetch in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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/ai.smithery%2Fsmithery-ai-fetch/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "smithery-ai-fetch": {
      "type": "http",
      "url": "https://server.smithery.ai/@smithery-ai/fetch/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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 listedRequired15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Smithery integrations