Productivity

streamsgrp.com

Provides access to contact and principal information for a consulting firm.

1 endpoint3 known toolsFirst detected June 16, 2026Last detected August 26, 2026

ENDPOINT 1

https://streamsgrp.com/mcp

No auth detected

MCP server metadata

Name: streamsgrp
Version: 0.1.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Streams Consulting Group MCP over streamable HTTP, per spec revision 2025-06-18. Five principals, six services, four practice sectors, and the firm contact record are queryable without authentication. Response format is driven by the Accept header. The server accepts application/json alone, text/event-stream alone, both together (any order, any q-values), */*, and absent Accept. JSON wins ties; q-values resolve unequal preferences. A request that accepts neither MIME type receives 406 Not Acceptable with a text/plain body — no JSON-RPC envelope, since the rejection is pre-JSON-RPC. Surface: 3 tools (list_principals, get_principal, get_contact) plus 4 concrete resources (streamsgrp://principals, streamsgrp://services, streamsgrp://sectors, streamsgrp://contact) and 2 resource templates (streamsgrp://principal/{slug}, streamsgrp://service/{slug}). Full schemas are on tools/list and resources/templates/list. Errors carry on two layers. Tool-level failures (unknown slug) return a CallToolResult with isError: true and a textual message — the JSON-RPC envelope itself is successful. Transport-level failures return JSON-RPC error envelopes at HTTP 200: -32700 parse error for malformed JSON, -32099 for rate-limit breach. The 406 Accept-header rejection is the one transport error that bypasses the JSON-RPC envelope. Rate limit is 60 requests per 60 seconds per IP, keyed on cf-connecting-ip (missing header falls back to a shared "anon" bucket). Spec revision is pinned to 2025-06-18; the /.well-known/mcp pointer advertises the same value, and the two are bumped in lockstep when the SDK is upgraded. Full contract at https://streamsgrp.com/mcp-docs.md

Known tools 3

list_principals

Return summaries of every principal at Streams Consulting Group.

Inferred read-only

get_principal

Return the full record for a single principal by slug.

Inferred read-only

get_contact

Return the firm contact record: primary contact (name, role, email, phone), opportunities URL, and response-window commitment.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.streamsgrp]
url = "https://streamsgrp.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "streamsgrp": {
      "type": "http",
      "url": "https://streamsgrp.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: streamsgrp
Remote MCP URL: https://streamsgrp.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "streamsgrp": {
      "url": "https://streamsgrp.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "streamsgrp": {
      "type": "http",
      "url": "https://streamsgrp.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "streamsgrp",
  "transport": "streamable-http",
  "url": "https://streamsgrp.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for streamsgrp.com was fetched 2026-08-23T18:32:46.984Z and is being refreshed.

Trust status Trusted

streamsgrp.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.