Reich Tools — Trademark Clearance & Stock Signals

io.github.sreichsbb-stackPublished by GitHub account sreichsbb-stackv1.0.0Updated Oct 24, 2026

Trademark clearance (USPTO+TMview) and self-graded stock signals for AI agents. JSON verdicts.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant trademark clearance verdicts for brand names and self-graded technical stock signals for US equities.

What you can do
Check a brand name for trademark collisions across USPTO and TMview, with phonetic and fuzzy matching, Nice-class inference, domain and social handle checks, and a composite CLEAR/CAUTION/HIGH_RISK/UNKNOWN grade plus alternative names that clear. Get BUY/SELL/HOLD technical signals for US stocks based on RSI, moving-average trend, momentum, volume and ATR-adjusted confidence, in batches of up to 10 symbols. Read a public performance track record of past signals resolved against later prices. Receive one structured JSON verdict per call, with honest failure states instead of fabricated data.
When to use it
Useful when vetting candidate brand or product names before launch, or when a finance-oriented assistant needs quick technical signals and a published track record for US stocks.
Requirements
A remote Streamable HTTP endpoint hosted on Apify; no local install. Authentication is required: OAuth sign-in to Apify on first connection, or an Apify API token sent in the Authorization header. Network access to the endpoint.
Before you install
Usage is paid per call: a fee per name verdict and a lower fee per stock signal, with failed lookups stated as not charged. An Apify account and OAuth sign-in or API token are needed, so treat the token as a secret. Signals are technical indicators, not investment advice, and results are sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Reich Tools — Trademark Clearance & Stock Signals in the dashboard and add it to a workspace.
  2. Connect the required 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/io.github.sreichsbb-stack%2Freich-tools/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "reich-tools-trademark-clearance-stock-si": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=shane_reich/name-clearance-verdict,shane_reich/stock-edge-signals"
    }
  }
}

README

Reich Tools MCP — Verification & Market Intelligence for AI Agents

Remote MCP server exposing two production tools, hosted on Apify's Streamable HTTP MCP infrastructure. No local install, no code — one URL. OAuth or API-token auth.

House rule: tools that tell you the truth. Both tools return honest failure states instead of fabricated data, and never charge for errors.

Quick start

Add to any MCP client (Claude Desktop, Claude.ai, Cursor, VS Code, or any Streamable HTTP client):

json
{  "mcpServers": {    "reich-tools": {      "url": "https://mcp.apify.com?tools=shane_reich/name-clearance-verdict,shane_reich/stock-edge-signals"    }  }}

On first connection you'll be prompted to sign in to Apify (OAuth). Alternatively, authenticate with a header: "headers": { "Authorization": "Bearer <APIFY_TOKEN>" }.

Tools

🏅 Name Clearance Verdict — shane_reich/name-clearance-verdict

One call answers: "Is this brand name safe to use?"

  • Trademark knockout across USPTO + TMview (70+ IP offices) with phonetic & fuzzy collision matching
  • Nice-class inference from your product description
  • RDAP domain availability + best-effort social handle checks
  • Composite grade: CLEAR / CAUTION / HIGH_RISK / UNKNOWN — never CLEAR if a trademark source failed
  • Alternative names that clear

→ Store listing · $0.10 per verdict · failed lookups never charged

📈 Stock Edge — shane_reich/stock-edge-signals

BUY/SELL/HOLD technical signals for US stocks — the only signal tool that grades its own homework. Every signal is written to a permanent ledger, resolved against subsequent prices daily, and published (wins and losses) via a free performance mode.

  • RSI, MA20/50 trend, momentum, volume confirmation, ATR-adjusted confidence
  • Multi-provider failover (Finnhub, Twelve Data, Alpha Vantage)
  • Batch up to 10 symbols; honest INSUFFICIENT_DATA states

→ Store listing · $0.015 per signal · free public track record · errors never charged

Why agents use these

Both tools return one structured, deterministic JSON verdict per call — no prose parsing, no pagination, no session state. Designed for agent workflows: brand-name vetting inside product-launch pipelines, portfolio monitoring inside finance agents.

Transport & compatibility

  • Transport: Streamable HTTP (hosted at mcp.apify.com)
  • Auth: OAuth or Authorization: Bearer <APIFY_TOKEN>
  • Clients tested: Claude Desktop, Claude.ai, Cursor, VS Code
  • Output schemas published (Actor output schema v1) so clients get structured results

Built and maintained by Shane Reich · Apify profile

Source: README.md at commit 1ae3c3e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 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

Other Signals integrations