ContentSweep Supplier Feeds

ai.contentsweepPublished by contentsweep.aiOfficial publisherv1.1.1Updated Nov 3, 2026

Map and validate recurring flat supplier catalogs with approved profiles and drift checks.

The publisher's own server: Content Sweep

VerifiedStreamable HTTPWeb executableData & Analytics

Server details

Identifier: ai.contentsweep/supplier-feeds
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 11, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to contentsweep.ai, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.contentsweep%2Fsupplier-feeds.svg)](https://sourceweft.com/mcp/ai.contentsweep%2Fsupplier-feeds?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP server that lets an assistant map and validate recurring flat supplier catalog files against approved profiles, with drift checks.

What you can do: Map incoming flat supplier catalog files to approved column profiles.
Validate recurring catalog imports against those profiles.
Detect drift between successive catalog deliveries and flag changes.
No individual tools are listed in the manifest, so exact operations are not documented.
When to use it: Useful when an assistant regularly handles flat supplier catalog files from the same sources and needs to check that each new delivery still matches an agreed structure before it is used.
Requirements: Remote streamable HTTP endpoint at mcp.contentsweep.ai; no local package or runtime. Requires an existing organization API key sent in the X-API-Key header.

Before you install

The server requires an organization API key in the X-API-Key header; treat it as a secret and share it only with a trusted client. Supplier catalog data is sent to a third-party hosted service, so confirm that is acceptable for your data. Tool behavior is not documented in the manifest, so verify whether operations write or change anything before relying on it.

Installation

In SourceWeft

Open ContentSweep Supplier Feeds in the dashboard and add it to a workspace.
Connect X-API-Key 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/ai.contentsweep%2Fsupplier-feeds/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": {
    "contentsweep-supplier-feeds": {
      "type": "http",
      "url": "https://mcp.contentsweep.ai/v1/feeds/mcp/",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

ContentSweep supplier-feed examples

Current status — November 1, 2026

Hosted engine feeds-1.0; MCP server reports 1.1.0 and the existing active Registry descriptor is 1.1.1. These version labels describe different artifacts. Five trials once per verified organization; $20/10 evaluations or $99/month for 100. Existing organization key required. Revised n8n entry 20893 was last recorded under review October 31; acceptance is pending.

Agent setup · Product skill · Task-to-tool reference. Skills support Codex and Claude Code and grant no upload, business-meaning approval, spending or destination-write permission. Historical test notes below retain their original scope; synthetic/internal qualification is not paid adoption.

Turn recurring supplier CSV/JSONL into an approved destination schema, validate the complete file, and stop for review when its source structure changes.

Offer and synthetic demo · Integration guide · Request a pilot

Historical recipe evidence records n8n 2.42.5 and an HTTPS first-import proof. Revised existing entry 20893 was last recorded under review October 31, 2026; acceptance is pending. Keep that entry rather than creating another submission.

approved-import.n8n.json: supplier feed → explicit mapping approval → validated JSONL.
drift-review.n8n.json: saved profile → changed source → review notification.
correction-replay.n8n.json: original rejection → corrected feed → re-evaluation.

Import an inactive workflow, set its Config values, and select an HTTP Header Auth credential named ContentSweep X-API-Key with header X-API-Key. Review field meanings, EUR currency, comma decimals, and contract rules before setting approvedByOperator=true. Use a fresh idempotency key per evaluation; retry the same request with its ORIGINAL quote and key. For recurring/corrected feeds, supply the saved profile ID. Correction replay also needs the original rejected job ID. Drift notification requires your SMTP credential and verified sender.

Reference HTTP client

Set CONTENTSWEEP_API_KEY in your environment. Run:

bash

python client.py --base-url https://mcp.contentsweep.ai# After reviewing mapping and spending decisions:python client.py --base-url https://mcp.contentsweep.ai --approve-mapping --approve-evaluation

python client.py --base-url https://mcp.contentsweep.ai# After reviewing mapping and spending decisions:python client.py --base-url https://mcp.contentsweep.ai --approve-mapping --approve-evaluation

The first command uploads the repository-owned fixture and prints the proposal. Evaluation requires an existing provisioned account and explicit flags. A completed rejection report uses one evaluation; previews and platform failures do not. Use the existing verified product account and live funding portal; purchases need separate authorization.

The approved fixture preserves SKU 000123 as a string and price 19.90 as an exact decimal string. normalized-example.jsonl is regenerated and checked before publication. These examples demonstrate supported behavior; they establish no comparative superiority or customer ROI.

Supported service bounds: flat UTF-8 CSV/JSONL, 10 MiB, 50,000 records. Raw uploads expire in 24 hours; results in seven days; job receipts in 30 days. Saved approved profiles remain until deletion. Use existing account authorization; never put real keys or customer files into examples.

MCP endpoint: https://mcp.contentsweep.ai/v1/feeds/mcp/ (Streamable HTTP). Authentication is an existing organization key via X-API-Key. OpenAPI, llms.txt, capabilities and emerging discovery metadata are available on the service domain.

The service is published in the official MCP Registry. Registry inclusion makes the descriptor available to clients that use that registry; configuring a client and obtaining account access are separate steps.

Release publication

The Publish verified MCP release action runs on feeds-v* tags and manual dispatch. The tag must match the reviewed version in server.json. It checks inactive example workflows, fixture output, deployed readiness and capability bounds, and the official descriptor schema. The official publisher is pinned to v1.8.1 with its SHA256 checksum. A domain-scoped Ed25519 secret is held in the contentsweep-distribution GitHub environment. Publication is read back from the registry; rerunning an identical version verifies it without another mutation, and conflicting immutable versions fail. Version updates still require a reviewed release; this action does not deploy the service.

For the first Creator Hub template, use the submission packet and approved-import.n8n.json. Submit later templates after the first is approved, following current new-creator guidance.

Example assets are published under Apache-2.0. The hosted service is operated separately. No customer files, contacts, keys, or private marketing records are included.

Source: README.md at commit d0c5f33

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v1.1.1LatestNov 3, 2026
v1.0.0Oct 11, 2026

Score

85% 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
License10 pts