Dev.to Security ๐Ÿ” Cybersecurity ๐Ÿ‘ 0 ๐Ÿ“– 2 min read

NoteDiscovery Separates Organization Login From MCP API Keys

NoteDiscovery Separates Organization Login From MCP API Keys NoteDiscovery is a Markdown knowledge library that can serve its content to people through a browser and to AI assistants through an MCP endpoint. That creat

NoteDiscovery Separates Organization Login From MCP API Keys

NoteDiscovery is a Markdown knowledge library that can serve its content to people through a browser and to AI assistants through an MCP endpoint. That creates two access paths with different clients and different credentials. The project's authentication documentation says browser users use the organization login while MCP servers, scripts, and automation should use an API key.

ZoomEye returned 47 title matches for title="NoteDiscovery", 64 HTTP-body matches, and no application fingerprint. The title query is selected because the product name is distinctive. The count identifies pages, not confirmed organizations or exposed note stores.

Two paths, two policy questions

The browser path needs session protection, organization membership, and note or workspace authorization. The MCP path needs API-key verification and a scope that defines which notes, attachments, and tools the assistant can reach. A valid key should not become an organization administrator session.

The project release notes say that when authentication is enabled, the MCP endpoint requires an API key or remains disabled. That is a safer default than a public endpoint, but operators still need to verify the deployed behavior. The wrong reverse-proxy route, an older build, or a disabled authentication setting can change the result.

Inventory every exposed document path

Record the organization hostname, MCP hostname, authentication mode, API-key owner and scope, and whether the MCP endpoint is enabled. Review reverse-proxy rules for both hostnames. Confirm that a request cannot switch from the organization login host to the API host with a copied cookie or header.

The notes and attachments are plain files in the documented storage model. Backup access is therefore part of the content boundary. Protect the data volume, encryption key, and backup destination with permissions that do not depend on the web application being online.

Verify the 47 title candidates

For each candidate, confirm ownership, page title, static assets, login behavior, and whether the site is a demonstration or documentation page. A title match does not prove that MCP is enabled. Use the selected count as the starting set and inspect the MCP endpoint only on owned hosts.

The zero application count is a coverage gap. Future reviews should look for a stable static asset or API signature and compare it with the title and body counts.

Respond to a key or session leak

If an API key was exposed, revoke it, review MCP requests, and identify the notes returned or changed. If a browser session was exposed, invalidate sessions and review organization membership. Rotate any credentials stored in note files or attachments if the content could be read.

Keep the human login and machine-key paths separate in logs. A report should show which identity read which document, not only that the service was reachable.

References

๐Ÿ“ฐ Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes โ€” full credit and traffic to the original publisher.