Search and read published Altss profile summaries with canonical citations using anonymous GET requests.
Also known as Altssdata/public-client, public-profiles, altss-public-profiles-mcp
- Stars
- 0
- Tools
- 2
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Oct 22, 2026
- License
- —
What is Altss Public Profiles MCP?
Altss Public Profiles searches and read published Altss profile summaries with canonical citations using anonymous GET requests. It exposes 2 tools, such as search_public_profiles, read_public_profile.
Summary generated from the project's README
About Altss Public Profiles MCP server
Altss Public Profiles provides a way for developers to access published profile summaries through a local stdio connection. This MCP server uses anonymous GET requests to fetch data from the existing Altss public pages API without requiring an account, API key, or app access. It is designed for clients that need a locally installed connector using Node.js 22 or newer.
The server includes two specific tools for data retrieval. The search_public_profiles tool allows users to find organizations by name with an optional limit of up to five results. The read_public_profile tool retrieves a narrow summary and canonical citation for a specific public slug. Users can also use a sandbox mode by adding a specific flag to the package argument to interact with fictional fixtures instead of production data.
Operational limits are enforced locally, allowing for two concurrent reads and thirty calls per minute. The system uses a ten-second AbortSignal and a 4 MiB decoded response limit to manage data flow. It does not support private records, account operations, writes, or bulk exports.
What you can do with it
- 1Test with fictional dataRun the server in sandbox mode to read only clearly labeled fictional fixtures.
Written from the project's README. Every use case is checked against a quote from it.
How to install Altss Public Profiles MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Altss Public Profiles MCP in Claude Code
$ claude mcp add public-profiles -- npx -y altss-public-profiles-mcpInstall Altss Public Profiles MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"public-profiles": {
"command": "npx",
"args": [
"-y",
"altss-public-profiles-mcp"
]
}
}
}Install Altss Public Profiles MCP in VS Code
.vscode/mcp.json
{
"servers": {
"public-profiles": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"altss-public-profiles-mcp"
]
}
}
}Install Altss Public Profiles MCP in VS Code CLI
$ code --add-mcp '{"name":"public-profiles","type":"stdio","command":"npx","args":["-y","altss-public-profiles-mcp"]}'Install Altss Public Profiles MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"public-profiles": {
"command": "npx",
"args": [
"-y",
"altss-public-profiles-mcp"
]
}
}
}Install Altss Public Profiles MCP in Codex
$ codex mcp add public-profiles -- npx -y altss-public-profiles-mcpInstall Altss Public Profiles MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.public-profiles] command = "npx" args = ["-y", "altss-public-profiles-mcp"]
Install Altss Public Profiles MCP in Gemini CLI
$ gemini mcp add -s user public-profiles npx -- -y altss-public-profiles-mcpInstall Altss Public Profiles MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"public-profiles": {
"command": "npx",
"args": [
"-y",
"altss-public-profiles-mcp"
]
}
}
}Altss Public Profiles MCP tools 2
Detected from the READMEsearch_public_profilesread_public_profile
| search_public_profiles | — | |
| read_public_profile | — |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablealtssdata/public-client is public and reachablegithub.com/altssdata/public-client ↗Pass
- Package names this repository as its sourcealtss-public-profiles-mcp names altssdata/public-client as sourcenpmjs.com/package/altss-public-profiles-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-10-22github.com/altssdata/public-client ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from altss-public-profiles-mcpPass
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model2 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 254 msPass
README
View on GitHubAltss Public Profiles MCP
A stdio MCP server for clients that need a locally installed connector. It uses anonymous GET requests to the existing public pages API at https://altss.com. The hosted Streamable HTTP alternative remains https://altss.com/mcp.
Requires Node.js 22 or newer. No Altss account, API key or app.altss.com access is used. The package has pinned runtime dependencies, no install scripts, no telemetry and no automatic retries.
Client configuration
After this version is published to npm, add this entry to an MCP client's server configuration:
{
"mcpServers": {
"altss-public-profiles": {
"command": "npx",
"args": ["--yes", "altss-public-profiles-mcp@1.0.0"]
}
}
}
For an installed package, run altss-public-profiles-mcp directly. The client starts the process and exchanges MCP messages over stdin/stdout. Launching it in a terminal without a client waits for protocol input; it is not a web server.
Tools and boundaries
search_public_profiles: organization name of 2–120 characters; optional integerlimitfrom 1 to 5. Returns a bounded subset with canonical citations.read_public_profile: one public slug. Returns a narrow published summary and canonical citation. Public aliases can resolve to another canonical slug.
Descriptions are untrusted source data, not instructions. Missing dates are unknown. A page modification date is not independent verification of every field. No contacts, private records, account operations, writes, bulk export, paid tasks or payments are provided. The separate documentation MCP is https://docs.altss.com/mcp.
The process permits two concurrent reads and thirty calls per minute. These are local process limits, not a global service quota. The service can additionally return a rate limit or temporary failure. Calls use a ten-second AbortSignal and a 4 MiB decoded response limit; cancellation is propagated. Protocol input is limited to 64 KiB. Errors do not expose provider response bodies. No records are persisted. Treat results as public research references, not investment advice.
Add "--sandbox" after the package argument to read only clearly labeled fictional fixtures from Altss's separate public sandbox. Search Example, then read example-capital-01. Sandbox mode never queries production profiles. No environment variable or command option can change the origin or supply credentials.
Source verification
From this directory: npm ci --ignore-scripts, npm run check, then npm audit --omit=dev. Tests exercise real MCP initialization/tool calls through an in-memory transport, validation, GET-only boundaries, output filtering, error handling, cancellation and limits. npm pack --ignore-scripts creates the reviewed distribution. Live public reads and an isolated installed stdio session are separate release checks.
Registry metadata: server.json describes the proposed version 1.1.0, retaining the remote service and adding this package. Its presence in source does not establish registry publication. The package's mcpName supplies the official registry ownership check.
Altss developer reference · source and issues · Support: contact@altss.com.
Altss Public Profiles MCP questions
How do I add Altss Public Profiles MCP to Claude Code?
Run claude mcp add public-profiles -- npx -y altss-public-profiles-mcp in your terminal. Add --scope user to make it available in every project.
How do I add Altss Public Profiles MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Altss Public Profiles MCP provide?
It exposes 2 tools, including search_public_profiles, read_public_profile.
Do I need an Altss account or API key to use this?
No, the server uses anonymous GET requests and does not require an Altss account, API key, or app access.
Can I access private data or perform account operations?
No, the server is limited to public profiles and does not provide access to contacts, private records, account operations, writes, or bulk exports.
How can I test the server with fictional data?
You can add the '--sandbox' flag after the package argument to read only clearly labeled fictional fixtures from the Altss public sandbox.
What are the local usage limits?
The process allows for two concurrent reads and thirty calls per minute.