{
  "markdown": "# Syracuse Company New MCP Server\n\nInstallation notes\n\n## API Key\n\nGet a free API key from syracuse.1145.am - all you need to provide is your email address. Here is a curl command to do so:\n\n```\ncurl -X POST \"https://syracuse.1145.am/api/v1/register-and-get-key/\" \\\n  -H \"Content-Type: application/json\" \\\n  -d \"{\\\"email\\\":\\\"your_email@example.com\\\"}\"\n```\n\nYou'll get a low usage level until you confirm the key, so make sure to use an email address that you have access to.\n\n## Using the MCP Server\n\nThere are 3 options:\n\n1. Run as a Local MCP Server (e.g. to connect with Claude Desktop)\n2. Connect via the Syracuse MCP server\n3. Run your own Remote MCP Server locally\n\n### To run as Local MCP Server\n\nPre-req: Install `uv` \n\n1. Clone this repo\n2. Copy `.env.sample` to `.env` and configure your MCP_SERVER_API_TOKEN with the API key you got above\n3. Example claude_desktop_config.json\n\n```\n{\n  \"mcpServers\": {\n    \"Syracuse Company News API\": {\n      \"command\": \"/path/to/uv\",\n      \"args\": [\n        \"--directory\",\n        \"/path/to/repo/syracuse-mcp-server\",\n        \"run\",\n        \"stdio_mcp_server.py\"\n      ]\n    }\n  }\n}\n```\n\n### To connect via Syracuse's MCP Server\n\nThere are no special pre-requisites\n\nConnect to `https://syracuse.1145.am/mcp` and provide your key as part of the authorization \n\nMCP doc is at `https://syracuse.1145.am/.well-known/mcp.json`\n\n### Running your own Remote MCP Server\n\nIf, for some reason, you want to run your own local MCP server then that is also possible. Again, it expects `uv`.\n\nYou don't need to update your key in the `.env` file, but you do need to: \n\n1. Clone this repo\n2. Copy `.env.sample` to `.env` - though any further configuration is not needed\n3. Run it with `uv run stateless_streaming_http_mcp_server.py`\n\nConnection info for MCP Inspector:\n- **Transport Type**: Streamable HTTP\n- **URL**: host:port/mcp, e.g. `http://127.0.0.1:9000/mcp`\n- Anyone making calls that require authorization will need to add their API key in the Authentication section\n\nThe Stateless Streaming MCP Server also serves an mcp.json at `.well-known/mcp.json` (in this example it would be `http://127.0.0.1/.well-known/mcp.json` )\n\n## Allowed tools\n\nBy default the ALLOWED_TOOLS restricts the MCP server to the minimum needed to register accounts and get stories:\n- register_and_get_key \n- location_groups_list\n- stories_industry_location_list\n- stories_organization_list\n\nThere's no problem to allow all tools - if you'd like to experiment simply remove ALLOWED_TOOLS from `.env`\n\n## Distinguishing tools that need auth\n\nEach tool is tagged with whether it requires authentication, derived from the OpenAPI `security` rules (an operation's `security` overrides the spec-level `security`, and an explicit empty `security: []` means no auth). This is exposed two ways:\n\n- In `tools/list`, each tool carries `_meta: { \"requiresAuth\": true | false }`.\n- In `.well-known/mcp.json`, the same `_meta` flag is present, and the `security` block is only attached to tools that actually require auth.\n\nClients can use this to call public endpoints without prompting the user for a token, and only request credentials for tools that need them.\n\n",
  "bytes": 3168,
  "sha": "b1b45ea6123aeee8af2f31c47df0ec4d073425c0978854bf5ccfbeeaba37c188",
  "repo_slug": "1145-am/syracuse-mcp-server",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_1145_am_syracuse_mcp_server_c6498ec3/readme"
}