Look twice.Find the gem.

AI agents and MCP servers, each published with its source and what the checks found.

Marketplace

  • Everything
  • AI agents
  • Apps
  • MCP servers
  • Templates
  • What people want
  • What changed this week
  • The verification standard
  • The ooruby Index
  • Servers that publish no source
  • Reliability guides
  • What the catalogue holds
  • Sell here

Our library

  • Everything, in one place
  • Guides
  • Glossary
  • Calculators
  • Checklists and cheat sheets
  • Community

ooruby

  • Home
  • For teams
  • Site status
  • Company projects
  • RSS feed

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.

Rubricv1.0
AI agentsAppsMCP serversTemplatesWantedCommunityOur library
Sign inSell
Catalogue/MCP servers/MCP Server Slack

MCP Server Slack

teamsparta · MCP server

MCP server for interacting with Slack

Not claimed by its maker.

SLMCP serverSupport

What else was checked

Publisher and name

  • Name matches another package once punctuation is ignoredIndistinguishable from mcp-server-slack to anyone typing quickly.

Maintenance

Abandoned

Last release 3 Jul 2025 (1.1.5), 455 days before this check on 1 Oct 2026.

Read from the npm registry's publish history, read by the nightly publisher check.

Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured

Not yet tested
Licence and provenance
finding
no LICENCE file at the root (.)
Tool description integrity
no match, 3 read
Pattern set 1.0 matched nothing across 3 descriptions, read 2026-10-04.
It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

  • ·Everything. Treat it as you would software from anywhere else.

Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

MCP server for interacting with Slack

Compare with

  • Slack MCP Serverside by side
  • Slack MCP Serverside by side
  • MCP Server Slackside by side
Compare all 4

How far this has been checked

Static scanned

What it establishes
Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not
How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read
Version 1.1.5, the file with digest sha512-UCFecRtqoNhQS+gPCUORlaOpqkoavy52GqT6GGSe/UuI1XRaSU1RV7UTWasT8gWUttCMLJaiiWL55sHKOaeG2Q==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
Authentication
Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
How the rungs work

Adding it

Paste this into your client's MCP configuration.

{
  "mcpServers": {
    "mcp-server-slack": {
      "command": "npx",
      "args": [
        "-y",
        "@teamsparta/mcp-server-slack@1.1.5"
      ]
    }
  }
}

Or run it directly.

npx -y @teamsparta/mcp-server-slack@1.1.5

Pinned to 1.1.5, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

47 installs last month · no published advisories · version current · checked 2026-10-02

Where this came from

Registry
npm
Package
@teamsparta/mcp-server-slack
Version read
1.1.5
Resolved
2026-08-30
Open the source(opens in a new tab)

No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/teamsparta-mcp-server-slack)](https://ooruby.com/market/teamsparta-mcp-server-slack)

About this listing

Kind
MCP server
Category
Support
Pricing
Free
Sandbox
No
Hosted
No
Updated
2026-08-24
Price
Free
Get it freeVisit maker
Rating
no reviews yet
0 want this so far
Sign in to vote

Sign in to watch this listing and hear when its version, rung or findings change.

Similar MCP servers

All MCP servers
GAMCP serverSupport
Clean scanStatic scanned

Server Gmail Autoauth MCP

gongrzhe
Free

Gmail MCP server with auto authentication support

112.1k installs/moISC
SLMCP serverSupport
2 findingsStatic scanned

Slack MCP Server

korotovsky
Free

Model Context Protocol (MCP) server for Slack Workspaces. This integration supports both Stdio and SSE transports, proxy settings and does not require any permissions or bots being created or approved

87.7k installs/moMIT
TCMCP serverSupport
4 findingsStatic scanned

MCP Ts Core

cyanheads
Free

Agent-native TypeScript framework for building MCP servers. Build tools, not infrastructure. Declarative definitions with auth, multi-backend storage, OpenTelemetry, and first-class support for Bun/No

60.9k installs/moApache-2.0

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.