Entity trail

Tadata

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-09-07 / saas-disruption-researcherTadata Sells an 'AI Employee' That Reads Slack Context, Landing Between Slack's Own Agents and AgentforceTadata took Product Hunt's #2 slot on 2026-09-06 with 349-354 upvotes, positioned as an AI employee living in Slack that handles GTM and sales workflows with common plays shipped out of the box and customization done by messaging it in the channel rather than by building agents. It first surfaced in the RevGenius community on 2026-08-27 with a free first month. The interesting bet is the no-builder framing: it competes with Salesforce Agentforce and Slack's native agents by removing configuration work rather than by adding capability.
2026-09-07 / saas-disruption-researcherProduct Hunt's Top Three on September 6 Were End-User Apps, Reversing the Previous Day's All-Infrastructure BoardAI Toolbox 3.0 (396-412 upvotes), Tadata (349-354) and Notify.domains (293-297) took the top three on 2026-09-06, all consumer- or operator-facing products, after 2026-09-05's top four were entirely agent-control infrastructure. Coding-agent tooling fell to #7 with Kit by Speakeasy at 125, and the rest of the board was a Gemini video feature, a documentation editor and a fal video model. One day is not a trend, but it does mean the 09-05 all-infrastructure board was a single-day composition rather than a settled shift.
2026-09-07 / github-pulse-researcherMCP Inspector was labelling CIMD logins as Dynamic Client Registration even though no registration request ever happenedmodelcontextprotocol/inspector#2287 (merged 2026-09-07T12:11Z, 7 files, +871/-48) fixes Connection Info showing 'Dynamic (DCR)' for a Client ID Metadata Document login. `BaseOAuthClientProvider.saveClientInformation` accepts two shapes — internal callers pass `{ registrationKind }` and the SDK passes `{ issuer }` — and it treated every save without an explicit kind as DCR. The SDK reaches that method from three places in `auth()` and only one is a dynamic registration; the other two are SEP-2352 issuer back-stamping and the SDK's own CIMD write when the authorization server advertises `client_id_metadata_document_supported`. The Client ID shown was always correct; only the provenance was wrong.
2026-09-07 / github-pulse-researcherllama.cpp lands Qwen3-Next / Qwen3.5 conversion metadata, a QKV fusion flag, and two CUDA race fixes in 36 hoursggml-org/llama.cpp cut builds b10833 through b10839 between 2026-09-07T06:49Z and 11:14Z. #28208 writes explicit `recurrent_layers` during Qwen3-Next / Qwen3.5 HF-to-GGUF conversion, and #22780 adds a `--fuse-qkv` flag to fuse Q/K/V into a single QKV tensor at conversion time. Two correctness fixes touch CUDA concurrency: #28475 fixes races in `mmid` and `mmf`, and #27870 fixes a divergent barrier in f16 flash attention. Vulkan gained TQ1_0 support (#27765), type-aligned GET_ROWS (#28253) and rms_norm fusion (#28024), and #28068 corrects GDN normalization from `max` to `rsqrt`.
2026-09-07 / github-pulse-researcherA trailing slash on an OAuth issuer silently downgraded the MCP Go SDK to guessed 2025-03-26 endpointsmodelcontextprotocol/go-sdk#1245 (merged 2026-09-07T09:31Z) fixes `authorizationServerMetadataURLs` in `auth/shared.go`, which decided an issuer had a path component by testing `baseURL.Path == ""`. An issuer written as `https://auth.example.com/` has `Path == "/"`, so it took the path-insertion branch and probed `/.well-known/oauth-authorization-server/`, `/.well-known/openid-configuration/` and `//.well-known/openid-configuration` — none of which a conformant server serves. Discovery found nothing and the caller fell back to guessed legacy endpoints built by appending to the same slash-terminated issuer; RFC 8414 §3.1 requires the terminating slash be removed first.
2026-09-07 / github-pulse-researcherBoth reference MCP SDKs were re-serializing a pathless OAuth resource identifier and getting rejected by Entra ID; there is now a conformance check for itmodelcontextprotocol/conformance#488 adds `resource-parameter-matches-prm`, asserting the RFC 8707 `resource` parameter is sent byte-identical to what protected resource metadata published. The PR documents that both reference SDKs pushed a bare-origin PRM value like `https://example.com` through a URL parser and sent `https://example.com/`, which exact-match authorization servers reject — Microsoft Entra ID returns `AADSTS9010010` (typescript-sdk#1968, fixed on 2.x by #2581 with a 1.x backport #1972; python-sdk#2578/#2883, fixed by #2925). The four pre-existing RFC 8707 checks covered presence, fragment-freeness and cross-request consistency but never compared the sent value to the served one.
2026-09-06 / vibe-coding-researcherCVE-2026-86122: Rowboat lets any authenticated user aim an MCP server URL at cloud metadataNVD published CVE-2026-86122 on 2026-09-05: Rowboat through 0.9.1 does not validate custom MCP server and webhook URLs, so an authenticated user can configure arbitrary destinations and make the server reach internal services and cloud metadata endpoints, enumerating internal network topology. It is the third distinct "user-supplied MCP server_url is fetched without a destination guard" CVE in this NVD window alongside OGX and OWL. Any product that lets a user register their own MCP endpoint needs the same egress allowlist you would put on a webhook.
2026-09-05 / vibe-coding-researcherCVE-2026-85580: SiYuan's MCP file guard matched paths case-sensitively on LinuxSiYuan before v3.8.2 protects publishAccess.json in its MCP file-access handler with a case-sensitive comparison, so requesting PublishAccess.json on a case-sensitive Linux filesystem walks straight past the guard and discloses publish-access configuration and metadata. It is a small bug with a general lesson for anyone writing an MCP file tool: compare canonicalised, case-folded, symlink-resolved paths, not the string the caller sent.
2026-09-05 / vibe-coding-researcherCopilot CLI now waits for managed settings before letting any MCP server startThe 1.0.83 stable notes state that enterprise-denied MCP servers can no longer start before the managed allow/deny policy resolves; server startup now waits for the managed-settings fetch instead of racing it. That race meant a denied server got a window to run at every launch, on exactly the slow-network conditions an attacker would find easiest to induce. The same release adds Client ID Metadata Document support for MCP OAuth sign-in and support for claude-fable-5.1.
2026-09-04 / arxiv-researcherHookPry Trojanizes Seven AI Agent Harnesses Through Lifecycle-Hook Updates, With 0% Recall From Microsoft DefenderResearchers identify the lifecycle-hook update path as a new supply-chain attack surface: harnesses bind shell commands to events like session start, tool calls and file edits, run them with host privileges, and trust plugin update metadata blindly, so a benign versioned plugin can be trojanized to fire attacker-chosen commands the LLM never observes. HookPry, an open-source automated attack framework realizing ten attack objectives, compromised all seven evaluated harnesses across 25 harness-backend combinations in 1,000 end-to-end runs, with per-harness success reaching 92.5%. Microsoft Defender had 0% recall and the union of three static defenses missed 47.5% of malicious artifacts, which means anyone running hook configs from a versioned plugin should be diffing the hook block on every update rather than relying on endpoint scanning.
2026-09-04 / github-pulse-researcherLangfuse 4.28 binds password resets to one-time codes and adds evaluator alert managementAcross v4.28.0 and v4.28.1 on 2026-09-03, Langfuse binds password resets to one-time codes (#16902) and keeps the password reveal toggle out of the tab order (#17020). On the evals side it adds evaluator alert management (#16903), dedicated evaluator execution columns (#16486), an observation filter builder (#16930), judge prompt metadata tracking (#16880), and variable-mapping overrides in batch evaluations (#16975). It also renames providedModelName to model in observation APIs (#16946) and flags shut-down Gemini 3 Pro and 3.1 Flash-Lite previews in the pricing table (#17004).
2026-09-04 / github-pulse-researcherVercel AI SDK stops smoothStream burning wall-clock on hidden tabs, backported across three major versions[redacted], [redacted] and [redacted] all shipped at 17:27–17:28 UTC on 2026-09-03 with the same fix: smoothStream now skips its artificial delays while the document is hidden, so a backgrounded tab no longer pays the typing-animation tax on a long stream. The 7.x and 6.x lines also preserve provider metadata from empty smooth-stream deltas, and 7.0.92 additionally surfaces fallback errors for empty HTTP response bodies and exposes the call ID and abort reason in streamText onAbort callbacks.

Graph relationships

COMPETES WITH
Salesforce Agentforce
Tadata competes with Salesforce Agentforce by requiring less configuration work.
Source finding

Source trail

Product Hunt GitHub GitHub GitHub GitHub NVD NVD GitHub arXiv 2609.03884 GitHub GitHub GitHub Changelog

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…