The Infxl Angle MCP server
com.infxl/angleinfxl.comstreamable-httpv1.1.0Scanned
Competitive-intelligence briefs on any company's rivals and market. OAuth sign-in or API key.
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the The Infxl Angle MCP server can do
The The Infxl Angle MCP server is published by infxl.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: check_company and request_brief), but cannot delete data. 4 tools only read.
2 tools bring in text other people can write (check_company and request_brief).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 2Claude Code: ask
check_companyCheck that a company's website is usable for a brief, before spending anything.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check that a company's website is usable for a brief, before spending anything. Pass the domain (acme.com) or any URL on it. Returns the normalised domain, the company name if this company has been seen before (otherwise null), and the credits available. Free: no credit is spent and no brief is started. Errors explain how to fix the input; URL_REDIRECTS_ELSEWHERE includes a suggested_url.
Annotations the server declares
- title: Check company
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
request_briefStart a competitive-intelligence brief for one company.Reads text others writeNo findings
Why it is in this group
- The name "request_brief" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Start a competitive-intelligence brief for one company. Returns at once with a brief_id; generation takes 3 to 6 minutes. Then call get_brief(brief_id) after poll_after_seconds. Cost: one credit is held now and spent only if the brief is ready with at least one item. An empty or failed brief costs nothing. Pass the same idempotency_key to retry safely: it returns the original brief instead of starting a second one. Needs OAuth sign-in or an API key. A client with OAuth sign-in asks the user to sign in the first time; a new account gets 1 free brief credit. For briefs on a schedule, the user can also subscribe at https://angle.app.infxl.com.
Annotations the server declares
- title: Request brief
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 4Show 4 read-only tools
get_accountShow this account: credits available, credits held by briefs in progress, the limits that apply, how this client is connected (API key or OAuth), and whether it is read-only.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it Show this account: credits available, credits held by briefs in progress, the limits that apply, how this client is connected (API key or OAuth), and whether it is read-only. Free.
Annotations the server declares
- title: Get account
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_briefGet the status of a brief started with request_brief and, once it is ready, the brief.No findings
Why it is in this group
- The name "get_brief" says "get": a word for reading.
Description, as the server wrote it Get the status of a brief started with request_brief and, once it is ready, the brief. While it is queued or generating, wait poll_after_seconds and call again. Call at most once every 15 seconds per brief. format: markdown (default, ready to relay in chat), json, or html (the full email render). structuredContent always holds the brief as JSON. Relay the markdown to the user unchanged, from the notice line to the footer: it is the whole brief, and it has no web page, so never link to the website as the brief. The brief states the date range its news is from; every item date falls inside it. The Focal Point names the most important development; the Wide Angle says what the news means together; each item's angle says what it means for the company and how to respond; Significance rates its urgency (CRITICAL, HIGH, MODERATE, LOW) and Signal type names the kind of move. empty means no news in the window and failed means it could not be generated; neither is charged.
Annotations the server declares
- title: Get brief
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_sample_briefReturn a sample of a finished brief, to see what request_brief and get_brief produce.No findings
Why it is in this group
- The name "get_sample_brief" says "get": a word for reading.
Description, as the server wrote it Return a sample of a finished brief, to see what request_brief and get_brief produce. Free, and works without an API key. format: markdown (default, what get_brief relays in chat), json, or html (the full email render). structuredContent always holds the brief as JSON, in the same shape as get_brief. It is an example from an earlier date, not news for the user: never present it as current.
Annotations the server declares
- title: Get sample brief
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_briefsList this account's briefs, newest first, with each brief_id, domain, status and creation time.No findings
Why it is in this group
- The name "list_briefs" says "list": a word for reading.
Description, as the server wrote it List this account's briefs, newest first, with each brief_id, domain, status and creation time. Briefs are kept for 30 days. Use get_brief(brief_id) to read one.
Annotations the server declares
- title: List briefs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:21 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.angle.app.infxl.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://auth.angle.app.infxl.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.angle.app.infxl.com/mcp: tools/list returned 6 tools to an anonymous client, including check_company (write), request_brief (write)
Posture changes
- Nov 16, 2026
- RFC 9728 protected resource metadata: none to https://mcp.angle.app.infxl.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://auth.angle.app.infxl.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://mcp.angle.app.infxl.com/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://auth.angle.app.infxl.com; Dynamic client registration: no…View diff
- RFC 9728 protected resource metadata: none to https://mcp.angle.app.infxl.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://auth.angle.app.infxl.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Tools2 changed.~2 changedView diff
- Changed:get_accountOnly readsdescription
- Changed:request_briefChanges thingsdescription
Tools1 added, 4 changed.+1 added~4 changedView diff
- Added:get_sample_briefOnly reads
- Changed:get_accountOnly readsannotations
- Changed:get_briefOnly readsannotations
- Changed:list_briefsOnly readsannotations
- Changed:request_briefChanges thingsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http angle https://mcp.angle.app.infxl.com/mcpclaude mcp add --transport http angle https://mcp.angle.app.infxl.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__angle__get_brief",
"mcp__angle__list_briefs",
"mcp__angle__get_account",
"mcp__angle__get_sample_brief"
],
"ask": [
"mcp__angle__check_company",
"mcp__angle__request_brief"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as angle. Review it before you use it.
Capability tags behind 2 rules
- mcp__angle__check_company untrusted-input
- mcp__angle__request_brief untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.infxl/angle/verify?hash=7701abcb18e83fffa0b015cb093ef25777dfcd75617098429f7e57649cfc0d04" | jq -e '.changed == false'Pinned hash 7701abcb18e8, from Nov 13, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.infxl/angle/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.infxl/angle)Source: MCP Registry. Synced Nov 13, 2026, 13:17 UTC.
The Infxl Angle MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the The Infxl Angle MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the The Infxl Angle MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the The Infxl Angle MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the The Infxl Angle MCP server have?
- 6 tools: 2 write, 4 read. check_company, request_brief, get_brief, list_briefs, get_account and get_sample_brief.
Does the The Infxl Angle MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the The Infxl Angle MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the The Infxl Angle MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.