Postman Echo Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

HTTP request echo from Postman Echo. No key required.

The publisher's own server: echo.email Deliverability Test

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant send HTTP requests to the Postman Echo service and inspect the echoed responses, with no API key required.

What you can do
This server connects an assistant to Postman Echo, a public service that returns the details of the HTTP requests it receives. The assistant can issue requests and read back the echoed method, headers, query parameters, and body, which is useful for checking how a request is formed. It runs locally over stdio and declares no authentication.
When to use it
Worth adding when you want an assistant to test or demonstrate HTTP request construction and see exactly what a server receives. It is a lightweight diagnostic aid rather than a tool for real APIs or production data.
Requirements
Runs as a local process on the user's machine via the npm package postman-echo-mcp over stdio, so Node.js and npm are needed. No accounts, API keys, environment variables, or headers are declared. Network access to the Postman Echo service is required.
Before you install
Requests are sent to a third-party public echo service, so anything placed in a request may be transmitted outside your machine; do not send secrets or private data. The server declares no authentication and no write access to your own systems.

Installation

In SourceWeft

  1. Open Postman Echo Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Echo integrations